From: Mathias Lafeldt <misfire@debugon.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: Annoated tag not found on git describe
Date: Wed, 27 Oct 2010 20:19:46 +0200 [thread overview]
Message-ID: <4CC86D42.20008@debugon.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1010271957520.28381@obet.zrqbmnf.qr>
On 10/27/2010 08:00 PM, Jan Engelhardt wrote:
> Hi,
>
>
> in the linux-manpages repository at
> git://git.kernel.org/pub/scm/docs/man-pages/man-pages , running git
> describe on the current HEAD (8482c7b836) produces
>
> fatal: No annotated tags can describe
> '8482c7b836a66f874e7dfea9c35fee4a82ad817b'.
> However, there were unannotated tags: try --tags.
>
> Which seems strange, given there is an annotated tag:
>
> (.git/refs/packed-refs)
> 45aba08f23aea4baf9ff5603cb5ec4ce148be2cc refs/tags/man-pages-3.29
> ^80786722b116f5002c28e9e0200044f825b236f6
>
> ==>
> object 80786722b116f5002c28e9e0200044f825b236f6
> type commit
> tag man-pages-3.29
> tagger Michael Kerrisk <mtk.manpages@gmail.com> 1287508632 +0200
>
> This is man-pages-3.29
>
> commit 80786722b116f5002c28e9e0200044f825b236f6
> tree 65ca9b696771fba53902a1342dc982066c9467e0
> parent 435070082d2694737825491cc47973626f352645
> author Michael Kerrisk <mtk.manpages@gmail.com> 1287508632 +0200
> committer Michael Kerrisk <mtk.manpages@gmail.com> 1287508632 +0200
>
> Ready for 3.29
>
>
>
> So what caused git 1.7.1 to get confused here?
>
>
> thanks,
> Jan
Hi,
must have been fixed in a later version, as it works for me:
$ git describe
man-pages-3.29-49-g8409222
$ git --version
git version 1.7.3.2
-Mathias
next prev parent reply other threads:[~2010-10-27 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 18:00 Annoated tag not found on git describe Jan Engelhardt
2010-10-27 18:19 ` Mathias Lafeldt [this message]
2010-10-27 19:24 ` Mathias Lafeldt
2010-10-27 19:55 ` 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=4CC86D42.20008@debugon.org \
--to=misfire@debugon.org \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.