From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Tommi Rantala <tt.rantala@gmail.com>
Cc: trinity@vger.kernel.org
Subject: Re: why does git describe shows 1.1-639-g4f6418b
Date: Mon, 29 Jul 2013 19:25:13 +0200 [thread overview]
Message-ID: <51F6A579.1040208@gmx.de> (raw)
In-Reply-To: <CA+ydwtrqzWfyOCufCJCP7ebhKCi4G_wQqsNVwHDuJGRAsmAxBw@mail.gmail.com>
On 07/29/2013 09:02 AM, Tommi Rantala wrote:
> 2013/7/27 Toralf Förster <toralf.foerster@gmx.de>:
>> and not something like v1.2-... ?
>
> It's because "v1.2" is a lightweight tag. Try:
>
> $ git describe --tags
> v1.2-7-g4f6418b
>
ah - thx
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
prev parent reply other threads:[~2013-07-29 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 15:51 why does git describe shows 1.1-639-g4f6418b Toralf Förster
2013-07-29 7:02 ` Tommi Rantala
2013-07-29 17:25 ` Toralf Förster [this message]
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=51F6A579.1040208@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@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