git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
FMFrancis Moreau <francis.moro@gmail.com>
Date
Jan 15, 2014, 09:59 UTC
Message-ID
<52D65C19.2000209@gmail.com>
In-Reply-To
<20140115094945.GD14335@sigill.intra.peff.net>
On 01/15/2014 10:49 AM, Jeff King wrote:
Show 20 quoted lines
> [+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.
Previous: Jeff KingNext: Junio C Hamano
Message 3 of 9 in “git-log --cherry-pick gives different results when using tag or tag^{}”
  1. Francis MoreauJan 10, 2014
  2. Jeff KingJan 15, 2014
  3. Francis MoreauJan 15, 2014
  4. Junio C HamanoJan 15, 2014
  5. revision: propagate flag bits from tags to pointeesJunio C Hamano, Jan 15, 2014
  6. Jeff KingJan 15, 2014
  7. Junio C HamanoJan 15, 2014
  8. Junio C HamanoJan 15, 2014
  9. Jeff KingJan 15, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.