From: Jan Engelhardt <jengelh@medozas.de>
Date: Mon, 23 Aug 2010 11:26:04 GMT
Subject: Re: git-describe --contains fails on given tree
Message-ID: <alpine.LNX.2.01.1008231324280.17348@obet.zrqbmnf.qr>
In-Reply-To: <201008222358.04504.trast@student.ethz.ch>

On Sunday 2010-08-22 23:58, Thomas Rast 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

Thanks for pointing that out.
(Ah the joy of BSD-inside-VMware.)

>Interestingly, --stdin disables this optimization:
>
>  $ git rev-parse v1.17~15^2^2 | git name-rev --stdin
>  95ce932690dfce8cbe50b6a3a8949e41a54c8966 (tags/v1.17~15^2^2)