git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: what exactly is git-tag looking for when you try to sign a tag?

From
Linus Torvalds <torvalds@osdl.org>
Date
Jan 15, 2006, 20:02 UTC
Message-ID
<Pine.LNX.4.64.0601151155520.13339@g5.osdl.org>
In-Reply-To
<200601151932.05342.alan@chandlerfamily.org.uk>
On Sun, 15 Jan 2006, Alan Chandler wrote:
Show 6 quoted lines
> 
> 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
Previous: Alan Chandler
Message 2 of 2 in “what exactly is git-tag looking for when you try to sign a tag?”
  1. Alan ChandlerJan 15, 2006
  2. Linus TorvaldsJan 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.