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

Re: Specifying revisions in the future

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Feb 5, 2012, 21:37 UTC
Message-ID
<m21uq9x8q2.fsf@igel.home>
In-Reply-To
<vpqipjlf309.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> "the successor of <commit>", OTOH, is not well defined, since there can
> be several successors, and one can't order them reliably (you can't
> really know the set of successors, because they can exist in different
> repositories).

Yet it would be nice to have a concise notation for "the nth successor of <commit> towards <commit>" (using --first-parent ordering when ambiguous).

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Matthieu MoyNext: Jakub Narebski
Message 4 of 16 in “Specifying revisions in the future”
  1. jpaugh@gmx.usFeb 4, 2012
  2. Jakub NarebskiFeb 5, 2012
  3. Matthieu MoyFeb 5, 2012
  4. Andreas SchwabFeb 5, 2012
  5. Jakub NarebskiFeb 5, 2012
  6. Andreas SchwabFeb 5, 2012
  7. Jakub NarebskiFeb 5, 2012
  8. Philip OakleyFeb 5, 2012
  9. Andreas SchwabFeb 5, 2012
  10. Miles BaderFeb 6, 2012
  11. Jonathan PaughFeb 7, 2012
  12. Matthieu MoyFeb 6, 2012
  13. Andreas SchwabFeb 6, 2012
  14. Andreas SchwabFeb 5, 2012
  15. Junio C HamanoFeb 5, 2012
  16. Jakub NarebskiFeb 5, 2012

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.