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

Re: identical hashes on two branches, but holes in git log

From
Junio C Hamano <gitster@pobox.com>
Date
May 21, 2015, 16:45 UTC
Message-ID
<xmqq1ti9lw0u.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20150521070523.GA8026@frolo.macqel>
Philippe De Muyter <phdm@macq.eu> writes:
> So we trade correctness for speed :(
No corretness is traded with anything else here.

There are applications where topology matters and where it doesn't. When topology really matters (e.g. drawing the graph), the caller can choose to use --topo-order to have git do the work. Of course the caller could accept output without --topo-order in streaming fashion and stitch the parent-child relationship itself.

And of course, in applications where topology does not matter, you do not have to wait.

That is called "choice", not "trading".
Previous: Philippe De Muyter
Message 15 of 15 in “identical hashes on two branches, but holes in git log”
  1. Philippe De MuyterMay 19, 2015
  2. Junio C HamanoMay 19, 2015
  3. Philippe De MuyterMay 19, 2015
  4. Junio C HamanoMay 19, 2015
  5. Philippe De MuyterMay 21, 2015
  6. Philip OakleyMay 21, 2015
  7. Philippe De MuyterMay 21, 2015
  8. Christian CouderMay 20, 2015
  9. Jeff KingMay 19, 2015
  10. Philippe De MuyterMay 20, 2015
  11. John KeepingMay 20, 2015
  12. Philippe De MuyterMay 20, 2015
  13. Jeff KingMay 20, 2015
  14. Philippe De MuyterMay 21, 2015
  15. Junio C HamanoMay 21, 2015

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.