From: Thomas Rast <trast@student.ethz.ch>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Jakub Narebski <jnareb@gmail.com>, <git@vger.kernel.org>
Subject: Re: git-describe --contains fails on given tree
Date: Sun, 22 Aug 2010 23:58:04 +0200 [thread overview]
Message-ID: <201008222358.04504.trast@student.ethz.ch> (raw)
In-Reply-To: <alpine.LSU.2.01.1008212241410.23864@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
>
> On Saturday 2010-08-21 21:55, Jakub Narebski wrote:
> >> for some reason, git-describe cannot figure out v1.17~15^2^2 in
> >> the pam_mount tree, despite me being able to actually give
> >> a description that would fit the contains syntax:
> >What does
> >
> > $ git describe --contains --tags v1.17~15^2^2
>
> "Cannot describe 95ce..."
>
> Funny thing is, describing "v1.17~15^2" does work, as does "v1.17~15^1".
That's clock skew:
$ git show -s --format="%cd" v1.17~15^2
Fri Jan 9 04:35:59 2009 +0100
$ git show -s --format="%cd" v1.17~15^2^2
Sat Jan 24 16:35:34 2009 +0100
Note how the parent commit is far newer than the child. git-name-rev
(which is what really drives git describe --contains) concludes that
it can stop searching along this line of history.
Interestingly, --stdin disables this optimization:
$ git rev-parse v1.17~15^2^2 | git name-rev --stdin
95ce932690dfce8cbe50b6a3a8949e41a54c8966 (tags/v1.17~15^2^2)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-08-22 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 19:47 git-describe --contains fails on given tree Jan Engelhardt
2010-08-21 19:55 ` Jakub Narebski
2010-08-21 20:42 ` Jan Engelhardt
2010-08-22 21:58 ` Thomas Rast [this message]
2010-08-23 11:26 ` Jan Engelhardt
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=201008222358.04504.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
--cc=jnareb@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).