我认为“git cherry-pick”只是破坏了一些东西

时间:2013-03-27 23:09:41

标签: git

我们的回购曾经是这样的:

* xxxxxxx (master, tag: v2.0.6c) Release v2.0.6c
|\
| * xxxxxxx (develop) Fixes and stuff
| * xxxxxxx Comment here
* | mmmmmmm (tag: v2.0.6b) Release v2.0.6b
|\|
| * xxxxxxx development branches!
. .

但现在我们的回购看起来像这样:

* f8cb1b7 (origin/master, master) Do something on develop
*   86848aa Merge branch 'master' of ssh://...
|\  
| *   f6f8733 (HEAD, tag: v2.0.6c) Release v2.0.6c
| |\  
| * \   30bd2f2 (tag: v2.0.6b) Release v2.0.6b
| |\ \  
| * \ \   68bbe5b (tag: v2.0.6a) Release v2.0.6a
| |\ \ \  
| * \ \ \   35ceefe (tag: v2.0.6) Release v2.0.6
| |\ \ \ \  
* | \ \ \ \   15decce Merge branch 'develop' of ssh://...
|\ \ \ \ \ \  
| |/ / / / /  
|/| | | | |   
* | | | | |   806eebe (tag: v2.0.5a) Release v2.0.5a
|\ \ \ \ \ \  
.... etc. Branches keep expanding outwards for each tag/commit

我所知道的是,有人试图挑选一个特定的提交,从开发到主人,承诺并推动它。尝试git reset --hard HEAD^似乎没有做任何事情,我对如何解决它感到茫然。

0 个答案:

没有答案