From: Andreas Krey <a.krey@gmx.de>
Date: Mon, 19 Jan 2015 16:10:18 GMT
Subject: Re: Regarding the determinacy of 'git describe'
Message-ID: <20150119161018.GA12632@inner.h.apk.li>
In-Reply-To: <20150116132917.GB7660@inner.h.apk.li>

On Fri, 16 Jan 2015 14:29:17 +0000, Andreas Krey wrote:
...
> === /tmp/tmp-ws-20150116-11355-v7zfcc
> 
> searching to describe HEAD
>  lightweight        4 r2.4/bl-0
>  lightweight        4 r2.4/bl-1
> traversed 5 commits
> r2.4/bl-0-4-g689e350

Apparently, this comes because two of the commit have the same timestamp,
affecting the log ordering (and presumably the order in which they
are used by 'git describe' as well). Also explains why it happens with
different probability on different machines.

But should 'git describe' behave this way?

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800