git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-log --cherry-pick gives different results when using tag or tag^{}
Date: Wed, 15 Jan 2014 10:59:53 +0100	[thread overview]
Message-ID: <52D65C19.2000209@gmail.com> (raw)
In-Reply-To: <20140115094945.GD14335@sigill.intra.peff.net>

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 --left-right v3.4.71-1^{}...next
>>
>> and
>>
>>     $ git log --oneline --cherry-pick --left-right v3.4.71-1...next
>>
>> give something different (where v3.4.71-1 is a tag).
>>
>> The command using ^{} looks the one that gives correct result I think.
> 
> Yeah, this looks like a bug. Here's a simple reproduction recipe:

Thanks a lot Jeff for your good analyze.

  reply	other threads:[~2014-01-15  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 13:15 git-log --cherry-pick gives different results when using tag or tag^{} Francis Moreau
2014-01-15  9:49 ` Jeff King
2014-01-15  9:59   ` Francis Moreau [this message]
2014-01-15 19:57   ` Junio C Hamano
2014-01-15 20:26     ` revision: propagate flag bits from tags to pointees Junio C Hamano
2014-01-15 21:56       ` Jeff King
2014-01-15 22:25         ` Junio C Hamano
2014-01-15 22:41           ` Junio C Hamano
2014-01-15 21:53     ` git-log --cherry-pick gives different results when using tag or tag^{} Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D65C19.2000209@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).