Eclipse Community Forums: EGit » Commit change in 2 branches

Help

Home

Home » Eclipse Projects » EGit » Commit change in 2 branches

Show: Today's Messages :: Show Polls :: Message Navigator

Commit change in 2 branches [message #1077900]

Fri, 02 August 2013 05:40

Marcus Warm
Messages: 9
Registered: July 2009
Location: Kevelaer, Germany

Junior Member

hi

we have to commit nearly all our changes in 2 (client specific) branches. Sometimes it's necessary to modify some (client specific) files for one branch before committing them.
What's the recommended way to do this? Cherry-Pick? Patch? Copy? ...
(With CVS we used the merge command and merged file by file. A lot of work.)

Regards
Marcus Warm Cool

mwvb.de/git

Eclipse Kepler 20130614-0229
EGit team provider 3.0.0.201306101825-r

[Eclipse Kepler 20130614-0229, EGit team provider 3.0.0.201306101825-r]

Report message to a moderator

Re: Commit change in 2 branches [message #1079811 is a reply to message #1077900]

Mon, 05 August 2013 01:33

Christian Halstrick is currently offline

Christian Halstrick
Messages: 85
Registered: July 2009

Member

One obvious solution is to do the change in one branch and then cherry pick that commit into the second branch. Branch specific modifications could be done afterwards in separate commits in the two branches.

Depending on how your two branches differ and how much branch specific work has to be done I could also imagine a solution:

        +--+--+--+--+--+ branch1
       /     /     /
      /     /     /
  +--+--+--+-----+ master
      \           \
       \           \
        +--+--------+--+--+ branch2

Here you do generic stuff always in a master branch, merge the master branch into branch1/2 from time to time and do specific stuff in branch1/2

Ciao
Chris

Report message to a moderator

Re: Commit change in 2 branches [message #1080062 is a reply to message #1079811]

Mon, 05 August 2013 08:25

Matthew Webber
Messages: 194
Registered: December 2010

Senior Member

>> Sometimes it's necessary to modify some (client specific) files for one branch before committing them.
If you do it like that, you have no way of telling whether a given commit has been made on both branches or not, and you lose many of the benefits of a version control system.

Christian's suggestion is an good one. You might also want to think about how your code is structured. If you have code that is almost the same on both branches, but has client-specific parts, you need to separate the common and client-specific parts. How to do this depends on the language you are using, and the nature of your application, but your question suggests that the code and build architecture needs re-thinking.

I hope that helps.

Matthew

Report message to a moderator

Previous Topic:	JGit - expose a commit's source tree as a filesystem to classpath
Next Topic:	JGit lacking full support for https?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Oct 07 16:50:49 EDT 2013