Re: git-log --cherry-pick gives different results when using tag or tag^{}

2014-01-15 Thread Jeff King
[+cc Junio, as the bug blames to him] On Fri, Jan 10, 2014 at 02:15:40PM +0100, Francis Moreau wrote: In mykernel repository, I'm having 2 different behaviours with git-log but I don't understand why: Doing: $ git log --oneline --cherry-pick --left-right v3.4.71-1^{}...next and

Re: git-log --cherry-pick gives different results when using tag or tag^{}

2014-01-15 Thread Francis Moreau
On 01/15/2014 10:49 AM, Jeff King wrote: [+cc Junio, as the bug blames to him] On Fri, Jan 10, 2014 at 02:15:40PM +0100, Francis Moreau wrote: In mykernel repository, I'm having 2 different behaviours with git-log but I don't understand why: Doing: $ git log --oneline --cherry-pick

Re: git-log --cherry-pick gives different results when using tag or tag^{}

2014-01-15 Thread Junio C Hamano
Jeff King p...@peff.net writes: [+cc Junio, as the bug blames to him] ... I think what is happening is that we used to apply the SYMMETRIC_LEFT flag directly to the commit. Now we apply it to the tag, and it does not seem to get propagated. The patch below fixes it for me, but I have no

Re: git-log --cherry-pick gives different results when using tag or tag^{}

2014-01-15 Thread Jeff King
On Wed, Jan 15, 2014 at 11:57:39AM -0800, Junio C Hamano wrote: Where do we pass down other flags from tags to commits? For example, if we do this: $ git log ^v1.8.5 master we mark v1.8.5 tag as UNINTERESTING, and throw that tag (not commit v1.8.5^0) into revs-pending.objects[].

git-log --cherry-pick gives different results when using tag or tag^{}

2014-01-10 Thread Francis Moreau
Hello, In mykernel repository, I'm having 2 different behaviours with git-log but I don't understand why: Doing: $ git log --oneline --cherry-pick --left-right v3.4.71-1^{}...next and $ git log --oneline --cherry-pick --left-right v3.4.71-1...next give something different (where