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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Philippe De Muyter <phdm@xxxxxxx> 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".

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]