Git merge/cherry-pick issue -


i using git large legacy project has 2 branches - v1.0 , v2.0. source each branch different in places, identical in others. when make bug fixes v1.0 branch have add them v2.0 branch using git cherry-pick git merge 1.0 trash large parts of v2.0 source.

however, new development has stopped on v1.0 , using git cherry-pick copy fixes v2.0 branch cumbersome. prefer somehow able tell git when git merge 1.0 -> 2.0 merge starting specific point in 1.0 commit history (i.e. when new development stopped). possible? allow me make multiple fixes v1.0 source , merge changes v2.0 in 1 hit instead of using multiple cherry-picks.

from 2.0 branch execute

git merge --strategy=ours v1.0 

i didn't tested myself try first on not important, docs need.

from documentation:

this resolves number of heads, resulting tree of merge of current branch head, ignoring changes other branches. meant used supersede old development history of side branches. note different -xours option recursive merge strategy.


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -