Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: Starting to bump Gnus version numbers again
Date: Sun, 20 Feb 2011 13:00:15 -0500	[thread overview]
Message-ID: <m3ipweio1k.fsf@jhcloos.com> (raw)
In-Reply-To: <m21v33axyy.fsf@whitebox.home> (Andreas Schwab's message of "Sun, 20 Feb 2011 09:53:25 +0100")

>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:

AS> James Cloos <cloos@jhcloos.com> writes:
>> Using a signed key makes <<git describe>> work best.

AS> You don't need to sign it, it just has to be annotated.

He is right.  I must have conflated the concepts of signed and annotated
tags at some point; I /had/ been thinking of them as identical.

So use:

   git tag -a <tagname>

to get an (unsigned) annotated tag.

Many projects use the tag name itself as the commit message for
annotated tags.  Or, if the tag is just the version, some use
the versioned name as the mesage, such as:

  git tag -a -m foobar-1.4.50 1.4.50

or the like.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2011-02-20 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20  1:11 Lars Ingebrigtsen
2011-02-20  7:28 ` James Cloos
2011-02-20  7:59   ` Lars Ingebrigtsen
2011-02-20  8:53   ` Andreas Schwab
2011-02-20 18:00     ` James Cloos [this message]
2011-02-20 23:39       ` jidanni
2011-02-21  0:01         ` Lars Ingebrigtsen
2011-02-23  2:27           ` jidanni
2011-02-21  2:24       ` Lars Ingebrigtsen
2011-02-21  3:27         ` Lars Ingebrigtsen
2011-02-21 19:11           ` Andreas Schwab
2011-02-21 23:08             ` Lars Ingebrigtsen
2011-02-21 23:23               ` Russ Allbery
2011-02-21 23:49                 ` Andreas Schwab
2011-02-22  0:02                   ` Lars Ingebrigtsen
2011-02-21 23:10             ` Lars Ingebrigtsen

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=m3ipweio1k.fsf@jhcloos.com \
    --to=cloos@jhcloos.com \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.org \
    /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).