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

Re: Unexpected behavior in git-rev-list

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 21, 2005, 18:45 UTC
Message-ID
<Pine.LNX.4.58.0509211144141.2553@g5.osdl.org>
In-Reply-To
<7vfyryw9ra.fsf@assigned-by-dhcp.cox.net>
On Wed, 21 Sep 2005, Junio C Hamano wrote:
>
> Ah, you told him to use 'rev-list --parents' and you can rewrite
> the list of parents there -- clever.
Exactly.

Yes, anything that would parse the "raw" commit information would be very lost indeed, and not able to figure out parenthood from the sparse list. But gitk already uses the "fakey" parents.

		Linus
Previous: Junio C HamanoNext: Daniel Barkalow
Message 7 of 9 in “Unexpected behavior in git-rev-list”
  1. Peter EriksenSep 18, 2005
  2. Linus TorvaldsSep 18, 2005
  3. Peter EriksenSep 18, 2005
  4. Peter EriksenSep 21, 2005
  5. Linus TorvaldsSep 21, 2005
  6. Junio C HamanoSep 21, 2005
  7. Linus TorvaldsSep 21, 2005
  8. Daniel BarkalowSep 22, 2005
  9. Linus TorvaldsSep 22, 2005

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.