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

git history order strange

From
JEJan Engelhardt <jengelh@computergmbh.de>
Date
Mar 10, 2008, 02:17 UTC
Message-ID
<Pine.LNX.4.64.0803100306420.21961@fbirervta.pbzchgretzou.qr>
Hi,

I have noticed that git-rev-list can output commit IDs in the wrong order. Steps to reproduce:

	git-clone git://git.kernel.org/pub/scm/git/git.git
	git-rev-list 3bddd7d
this will output
	...lots of IDs...
	8e1454b5ad285ec5dd25758e799c589045aff9d4
	6b7d25d97bdb8a26719f90d17ff5c9720be68762
	...lots of more IDs...

but this order seems to be the wrong way around, as 8e14 is the parent of 6b7d:

	git-log --pretty=raw 6b7d25d
	commit 6b7d25d97bdb8a26719f90d17ff5c9720be68762
	tree 661dce6a7e0f319fa1c53eb94c34585ee52190e4
	parent 8e1454b5ad285ec5dd25758e799c589045aff9d4

To be noted that it only happens with `git-rev-list`, but not with `git-rev-list --date-order` or `git-rev-list --topo-order`. Is it a bug in git-rev-list w/o arguments, or do I have to expect commits in random reverse order?

thanks, Jan

Next: Linus Torvalds
Message 1 of 2 in “git history order strange”
  1. Jan EngelhardtMar 10, 2008
  2. Linus TorvaldsMar 10, 2008

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.