Re: [RFC/PATCH] Option to revert order of parents in merge commit

2012-11-26 Thread Aaron Schrab
At 09:58 -0800 26 Nov 2012, Junio C Hamano wrote: Kacper Kornet writes: The change of order of parents happens at the very last moment, so "ours" in merge options is local version and "theirs" upstream. That may be something that wants to go to the proposed commit log message. I am neutral

Re: [RFC/PATCH] Option to revert order of parents in merge commit

2012-11-26 Thread Junio C Hamano
Kacper Kornet writes: >> Is there any interaction between this "pull --reverse-parents" >> change and possible conflict resolution when the command stops and >> asks the user for help? For example, whom should "--ours" and "-X >> ours" refer to? Us, or the upstream? > > The change of order of p

Re: [RFC/PATCH] Option to revert order of parents in merge commit

2012-11-26 Thread Kacper Kornet
On Fri, Nov 23, 2012 at 06:58:49PM -0800, Junio C Hamano wrote: > Kacper Kornet writes: > > The following patch is an attempt to implement this idea. > I think "revert" is a wrong word (implying you have already done > something and you are trying to defeat the effect of that old > something), a

Re: [RFC/PATCH] Option to revert order of parents in merge commit

2012-11-23 Thread Junio C Hamano
Kacper Kornet writes: > The following patch is an attempt to implement this idea. I think "revert" is a wrong word (implying you have already done something and you are trying to defeat the effect of that old something), and you meant to say "reverse" (i.e. the opposite of normal) or something.

[RFC/PATCH] Option to revert order of parents in merge commit

2012-11-23 Thread Kacper Kornet
When the changes are pushed upstream, and in the meantime someone else updated upstream branch git advises to use git pull. This results in history: ---A---B---C-- \ / D---E where B is my commit. D, E are commits pushed by someone else when I was working on B. However