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

Re: [PATCH] Stop git-rev-list at sha1 match

From
TGThomas Gleixner <tglx@linutronix.de>
Date
May 12, 2005, 00:31 UTC
Message-ID
<1115857873.22180.253.camel@tglx>
In-Reply-To
<20050511234455.GL22686@pasky.ji.cz>
On Thu, 2005-05-12 at 01:44 +0200, Petr Baudis wrote:
> for extensive discussion on how (it is impossible or very hard) to do
> better.
:)
> So how would you order the list of commits?
Rn
  merged Mn
  merged Mn-1
Rn-1
....

That's the relevant information in repository R. Looking at it from repository M after M updated to Rn

(Mn+1) == Rn	; Mn+1 is not created due to head forward
  merged Rn
  .. 
  merged Rn-3
Mn
Mn-1

Thats the historical correct ordering from a repository point of view. Thats the only relevant information IMNSHO.

The dates of author and committer are retrievable in each repository, but the order of commits are not.

tglx
Previous: Petr BaudisNext: Petr Baudis
Message 10 of 13 in “Stop git-rev-list at sha1 match”
  1. Stop git-rev-list at sha1 matchThomas Gleixner, May 11, 2005
  2. Junio C HamanoMay 11, 2005
  3. Thomas GleixnerMay 11, 2005
  4. Junio C HamanoMay 11, 2005
  5. Petr BaudisMay 11, 2005
  6. Thomas GleixnerMay 11, 2005
  7. Petr BaudisMay 11, 2005
  8. Thomas GleixnerMay 11, 2005
  9. Petr BaudisMay 11, 2005
  10. Thomas GleixnerMay 12, 2005
  11. Petr BaudisMay 13, 2005
  12. Junio C HamanoMay 12, 2005
  13. Junio C HamanoMay 12, 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.