From: Andreas Krey <a.krey@gmx.de>
To: git@vger.kernel.org
Subject: Re: Regarding the determinacy of 'git describe'
Date: Mon, 19 Jan 2015 17:10:18 +0100 [thread overview]
Message-ID: <20150119161018.GA12632@inner.h.apk.li> (raw)
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
prev parent reply other threads:[~2015-01-19 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 13:01 Regarding the determinacy of 'git describe' Andreas Krey
2015-01-16 13:29 ` Andreas Krey
2015-01-19 16:10 ` Andreas Krey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150119161018.GA12632@inner.h.apk.li \
--to=a.krey@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox