From: Johannes Sixt <j6t@kdbg.org>
Date: Wed, 27 Apr 2011 19:39:50 GMT
Subject: Re: Difference between --date-order and reverse chronological order?
Message-ID: <4DB87106.9030209@kdbg.org>
In-Reply-To: <7v7haf8ulj.fsf@alter.siamese.dyndns.org>

Am 27.04.2011 19:36, schrieb Junio C Hamano:
> Dun Peal <dunpealer@gmail.com> writes:
> 
>> But by Git's definition, for a child commit to be created, its parent
>> must already exist. So even in reverse chronological order, all
>> parents should come after all their children, no?
> 
> I think "distributed" and "your clock may be skewed" would solve that
> puzzlement ;-)

Are you saying that given this history:

      E----D
    /     /
   A--B--C

* we can get D-C-B-E-A or D-E-C-B-A with --topo-order

* we can get the above plus D-C-E-B-A with --date-order

* and with neither --topo-order nor --date-order we can also get
D-E-A-C-B or D-C-B-A-E if there was sufficient clock skew when the
commits were created. How would such a clock skew have looked like?

-- Hannes