git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-describe --contains fails on given tree

From
JEJan Engelhardt <jengelh@medozas.de>
Date
Aug 21, 2010, 20:42 UTC
Message-ID
<alpine.LSU.2.01.1008212241410.23864@obet.zrqbmnf.qr>
In-Reply-To
<m3occvoi5c.fsf@localhost.localdomain>
On Saturday 2010-08-21 21:55, Jakub Narebski wrote:
Show 22 quoted lines
>> 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:
>> 
>> $ git clone
>> git://pam-mount.git.sf.net/gitroot/pam-mount/pam-mount
>> Initialized empty Git repository in /dev/shm/pam-mount/.git/
>> remote: Counting objects: 7261, done.
>> remote: Compressing objects: 100% (1819/1819), done.
>> remote: Total 7261 (delta 5557), reused 6990 (delta 5348)
>> Receiving objects: 100% (7261/7261), 1.40 MiB | 832 KiB/s, done.
>> Resolving deltas: 100% (5557/5557), done.
>> 
>> $ cd pam-mount/
>> $ git describe --contains v1.17~15^2^2
>> fatal: cannot describe '95ce932690dfce8cbe50b6a3a8949e41a54c8966'
>> 
>> (Expected to get back: v1.17~15^2^2)
>> 
>> Why would it not want to return something? Possible bug?
>
>Is v1.17 an *annotated* tag?
It certainly is (if it were not, there be no tag, just commit):
$ git show v1.17
tag v1.17
Tagger: Jan Engelhardt <jengelh@medozas.de>
Date:   Mon Jan 26 00:41:17 2009 +0100
pam_mount 1.17
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkl8+J8ACgkQ92gFgoRMQ2Dd7QCeJj/u543aBiK/Los8LgvdkR/1 6nwAnA/CB23vjxFpVWsKZIW99GHxDglX =yLqV -----END PGP SIGNATURE-----

>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".
Previous: Jakub NarebskiNext: Thomas Rast
Message 3 of 5 in “git-describe --contains fails on given tree”
  1. Jan EngelhardtAug 21, 2010
  2. Jakub NarebskiAug 21, 2010
  3. Jan EngelhardtAug 21, 2010
  4. Thomas RastAug 22, 2010
  5. Jan EngelhardtAug 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.