From: "Carlos Martín Nieto" <cmn@elego.de>
To: John Stean <john.stean@lane15.co.uk>
Cc: git@vger.kernel.org
Subject: Re: question re tags
Date: Fri, 08 Mar 2013 17:30:20 +0100 [thread overview]
Message-ID: <1362760220.3681.1.camel@centaur.cmartin.tk> (raw)
In-Reply-To: <25720629.116.1362755762863.JavaMail.User@LANE15-HP>
On Fri, 2013-03-08 at 15:16 +0000, John Stean wrote:
> Ive been tagging some commits using tortoise git , for example with
> "v1.0", "v1.1" etc. In tortoise git log the tag sits alongside the
> commit as I expect.
> But when I do a git describe it outputs the first tag along with the
> latest commit. What am I doing wrong?
Those tags are probably lightweight tags, so by default git-describe
doesn't take them into account. You can pass the --tags flag to tell it
to consider lightweight tags as well.
cmn
prev parent reply other threads:[~2013-03-08 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 15:16 question re tags John Stean
2013-03-08 16:30 ` Carlos Martín Nieto [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=1362760220.3681.1.camel@centaur.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=john.stean@lane15.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).