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

Re: Can someone explain this git-blame/git-rev behavior to me?

From
Johannes Sixt <j.sixt@eudaptics.com>
Date
Jul 16, 2007, 13:24 UTC
Message-ID
<469B71A5.D5299A80@eudaptics.com>
In-Reply-To
<86sl7oaasx.fsf@lola.quinscape.zz>
David Kastrup wrote:
Show 15 quoted lines
> git-name-rev b5dd9d20
> b5dd9d20 tags/v1.4.2-rc1~88
> 
> So what is it I am doing wrong here?  The problem I have is that in
> Emacs, one can go to the "next version" in an annotated file, and I
> get stuck in a loop here, since tags/v1.4.2-rc1~88 delivers
> 
> git-rev-list HEAD --not tags/v1.4.2-rc1~88 --parents contrib/emacs/vc-git.el|tail -1|git-name-rev --stdin
> 
> d87b90e47f7430455385edcf8506288b9a73d3b5 (tags/v1.4.2-rc1~87) b5dd9d2027c1bd5758033c7baf6d087752b0263d (tags/v1.4.2-rc1~88) 280242d1cc1fe2847f649d2f16b273e168fcbc48 (tags/v1.4.2-rc1~92)
> 
> So we have tags/v1.4.2-rc1~87 listed as successor again, so I get into
> a loop of blame.
> 
> Is there something I don't understand about merges?

rev-list --parents list both the commit and its parent(s). If you are only interested in the parents, ignore the first SHA1 on the line.

-- Hannes
Previous: David KastrupNext: Junio C Hamano
Message 2 of 5 in “Can someone explain this git-blame/git-rev behavior to me?”
  1. David KastrupJul 16, 2007
  2. Johannes SixtJul 16, 2007
  3. Junio C HamanoJul 16, 2007
  4. David KastrupJul 17, 2007
  5. David KastrupJul 16, 2007

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.