git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: git@vger.kernel.org
Subject: Re: what exactly is git-tag looking for when you try to sign a tag?
Date: Sun, 15 Jan 2006 12:02:27 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601151155520.13339@g5.osdl.org> (raw)
In-Reply-To: <200601151932.05342.alan@chandlerfamily.org.uk>



On Sun, 15 Jan 2006, Alan Chandler wrote:
> 
> git-tag -s v1.0
> 
> and it complained that I don't have any secret key available.
> 
> What exactly is the process of making one available?

Do 

	gpg --list-secret-keys

to check what keys you have available to sign with.

Then, use

	git tag -u "key user name" v1.0

because what has _probably_ happened is that if you just use "-s" it will 
pick your "committer name" as the key identifier, and you probably made 
your keys using your real email or other identifier.

So "-u <username>" means the same thing as "-s", but with additionally 
specifying _which_ key it should use.

Alternatively, you should be able to just use "gpg --edit-key <keyname>" 
and then using "adduid" to add your git committer ID as a user of the key. 
At which point "git tag -s <tagname>" should just work, since gpg will be 
able to match up the keys automatically.

		Linus

      reply	other threads:[~2006-01-15 20:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 19:32 what exactly is git-tag looking for when you try to sign a tag? Alan Chandler
2006-01-15 20:02 ` Linus Torvalds [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=Pine.LNX.4.64.0601151155520.13339@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=alan@chandlerfamily.org.uk \
    --cc=git@vger.kernel.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).