{"thread":{"id":"24820","subject":"git-describe --contains fails on given tree","startedAt":"2010-08-21T19:47:46Z","lastAt":"2010-08-23T11:26:04Z","messageCount":5,"participants":["Jan Engelhardt","Jakub Narebski","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"148680","messageId":"alpine.LSU.2.01.1008212145520.14934@obet.zrqbmnf.qr","threadId":"24820","inReplyTo":null,"subject":"git-describe --contains fails on given tree","fromName":"Jan Engelhardt","fromEmail":"jengelh@medozas.de","sentAt":"2010-08-21T19:47:46Z","receivedAt":"2010-08-21T19:47:46Z","isPatch":false,"sender":{"key":"jengelh@medozas.de","avatar":null},"body":"Hi,\n\n\n\nfor some reason, git-describe cannot figure out v1.17~15^2^2 in\nthe pam_mount tree, despite me being able to actually give\na description that would fit the contains syntax:\n\n$ git clone\ngit://pam-mount.git.sf.net/gitroot/pam-mount/pam-mount\nInitialized empty Git repository in /dev/shm/pam-mount/.git/\nremote: Counting objects: 7261, done.\nremote: Compressing objects: 100% (1819/1819), done.\nremote: Total 7261 (delta 5557), reused 6990 (delta 5348)\nReceiving objects: 100% (7261/7261), 1.40 MiB | 832 KiB/s, done.\nResolving deltas: 100% (5557/5557), done.\n\n$ cd pam-mount/\n$ git describe --contains v1.17~15^2^2\nfatal: cannot describe '95ce932690dfce8cbe50b6a3a8949e41a54c8966'\n\n(Expected to get back: v1.17~15^2^2)\n\nWhy would it not want to return something? Possible bug?\n\nUsing git 1.7.1 on openSUSE 11.3.\n\n\nthanks,\nJan\n"},{"id":"148681","messageId":"m3occvoi5c.fsf@localhost.localdomain","threadId":"24820","inReplyTo":"alpine.LSU.2.01.1008212145520.14934@obet.zrqbmnf.qr","subject":"Re: git-describe --contains fails on given tree","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-08-21T19:55:53Z","receivedAt":"2010-08-21T19:55:53Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Jan Engelhardt writes:\n\n> Hi,\n> \n> \n> \n> for some reason, git-describe cannot figure out v1.17~15^2^2 in\n> the pam_mount tree, despite me being able to actually give\n> a description that would fit the contains syntax:\n> \n> $ git clone\n> git://pam-mount.git.sf.net/gitroot/pam-mount/pam-mount\n> Initialized empty Git repository in /dev/shm/pam-mount/.git/\n> remote: Counting objects: 7261, done.\n> remote: Compressing objects: 100% (1819/1819), done.\n> remote: Total 7261 (delta 5557), reused 6990 (delta 5348)\n> Receiving objects: 100% (7261/7261), 1.40 MiB | 832 KiB/s, done.\n> Resolving deltas: 100% (5557/5557), done.\n> \n> $ cd pam-mount/\n> $ git describe --contains v1.17~15^2^2\n> fatal: cannot describe '95ce932690dfce8cbe50b6a3a8949e41a54c8966'\n> \n> (Expected to get back: v1.17~15^2^2)\n> \n> Why would it not want to return something? Possible bug?\n\nIs v1.17 an *annotated* tag? What does\n\n $ git describe --contains --tags v1.17~15^2^2\n\nreturn?\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"148687","messageId":"alpine.LSU.2.01.1008212241410.23864@obet.zrqbmnf.qr","threadId":"24820","inReplyTo":"m3occvoi5c.fsf@localhost.localdomain","subject":"Re: git-describe --contains fails on given tree","fromName":"Jan Engelhardt","fromEmail":"jengelh@medozas.de","sentAt":"2010-08-21T20:42:42Z","receivedAt":"2010-08-21T20:42:42Z","isPatch":false,"sender":{"key":"jengelh@medozas.de","avatar":null},"body":"\nOn Saturday 2010-08-21 21:55, Jakub Narebski wrote:\n>> for some reason, git-describe cannot figure out v1.17~15^2^2 in\n>> the pam_mount tree, despite me being able to actually give\n>> a description that would fit the contains syntax:\n>> \n>> $ git clone\n>> git://pam-mount.git.sf.net/gitroot/pam-mount/pam-mount\n>> Initialized empty Git repository in /dev/shm/pam-mount/.git/\n>> remote: Counting objects: 7261, done.\n>> remote: Compressing objects: 100% (1819/1819), done.\n>> remote: Total 7261 (delta 5557), reused 6990 (delta 5348)\n>> Receiving objects: 100% (7261/7261), 1.40 MiB | 832 KiB/s, done.\n>> Resolving deltas: 100% (5557/5557), done.\n>> \n>> $ cd pam-mount/\n>> $ git describe --contains v1.17~15^2^2\n>> fatal: cannot describe '95ce932690dfce8cbe50b6a3a8949e41a54c8966'\n>> \n>> (Expected to get back: v1.17~15^2^2)\n>> \n>> Why would it not want to return something? Possible bug?\n>\n>Is v1.17 an *annotated* tag?\n\nIt certainly is (if it were not, there be no tag, just commit):\n\n$ git show v1.17\ntag v1.17\nTagger: Jan Engelhardt \nDate: Mon Jan 26 00:41:17 2009 +0100\n\npam_mount 1.17\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v2.0.9 (GNU/Linux)\n\niEYEABECAAYFAkl8+J8ACgkQ92gFgoRMQ2Dd7QCeJj/u543aBiK/Los8LgvdkR/1\n6nwAnA/CB23vjxFpVWsKZIW99GHxDglX\n=yLqV\n-----END PGP SIGNATURE-----\n\n>What does\n>\n> $ git describe --contains --tags v1.17~15^2^2\n\n\"Cannot describe 95ce...\"\n\nFunny thing is, describing \"v1.17~15^2\" does work, as does \"v1.17~15^1\".\n"},{"id":"148722","messageId":"201008222358.04504.trast@student.ethz.ch","threadId":"24820","inReplyTo":"alpine.LSU.2.01.1008212241410.23864@obet.zrqbmnf.qr","subject":"Re: git-describe --contains fails on given tree","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-08-22T21:58:04Z","receivedAt":"2010-08-22T21:58:04Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Jan Engelhardt wrote:\n> \n> On Saturday 2010-08-21 21:55, Jakub Narebski wrote:\n> >> for some reason, git-describe cannot figure out v1.17~15^2^2 in\n> >> the pam_mount tree, despite me being able to actually give\n> >> a description that would fit the contains syntax:\n> >What does\n> >\n> > $ git describe --contains --tags v1.17~15^2^2\n> \n> \"Cannot describe 95ce...\"\n> \n> Funny thing is, describing \"v1.17~15^2\" does work, as does \"v1.17~15^1\".\n\nThat's clock skew:\n\n $ git show -s --format=\"%cd\" v1.17~15^2 \n Fri Jan 9 04:35:59 2009 +0100\n\n $ git show -s --format=\"%cd\" v1.17~15^2^2\n Sat Jan 24 16:35:34 2009 +0100\n\nNote how the parent commit is far newer than the child. git-name-rev\n(which is what really drives git describe --contains) concludes that\nit can stop searching along this line of history.\n\nInterestingly, --stdin disables this optimization:\n\n $ git rev-parse v1.17~15^2^2 | git name-rev --stdin\n 95ce932690dfce8cbe50b6a3a8949e41a54c8966 (tags/v1.17~15^2^2)\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"148742","messageId":"alpine.LNX.2.01.1008231324280.17348@obet.zrqbmnf.qr","threadId":"24820","inReplyTo":"201008222358.04504.trast@student.ethz.ch","subject":"Re: git-describe --contains fails on given tree","fromName":"Jan Engelhardt","fromEmail":"jengelh@medozas.de","sentAt":"2010-08-23T11:26:04Z","receivedAt":"2010-08-23T11:26:04Z","isPatch":false,"sender":{"key":"jengelh@medozas.de","avatar":null},"body":"On Sunday 2010-08-22 23:58, Thomas Rast wrote:\n>> On Saturday 2010-08-21 21:55, Jakub Narebski wrote:\n>> >> for some reason, git-describe cannot figure out v1.17~15^2^2 in\n>> >> the pam_mount tree, despite me being able to actually give\n>> >> a description that would fit the contains syntax:\n>> >What does\n>> >\n>> > $ git describe --contains --tags v1.17~15^2^2\n>> \n>> \"Cannot describe 95ce...\"\n>> \n>> Funny thing is, describing \"v1.17~15^2\" does work, as does \"v1.17~15^1\".\n>\n>That's clock skew:\n>\n> $ git show -s --format=\"%cd\" v1.17~15^2 \n> Fri Jan 9 04:35:59 2009 +0100\n>\n> $ git show -s --format=\"%cd\" v1.17~15^2^2\n> Sat Jan 24 16:35:34 2009 +0100\n\nThanks for pointing that out.\n(Ah the joy of BSD-inside-VMware.)\n\n>Interestingly, --stdin disables this optimization:\n>\n> $ git rev-parse v1.17~15^2^2 | git name-rev --stdin\n> 95ce932690dfce8cbe50b6a3a8949e41a54c8966 (tags/v1.17~15^2^2)\n"}]}