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

Re: signing tags: user.name assumed to be gpg uid?

From
Peter Vereshagin <peter@vereshagin.org>
Date
Dec 30, 2009, 10:47 UTC
Message-ID
<20091230104720.GA3229@screwed.box>
In-Reply-To
<7vaax1bi3e.fsf@alter.siamese.dyndns.org>

Oh Junio want you buy me a mersedes benz? 2009/12/29 13:12:05 -0800 Junio C Hamano <gitster@pobox.com> => To Peter Vereshagin :

JCH> > I notice that after I init and config user.name and user.email the JCH> > user.comment gets taken from ~/.gpg automatically. JCH> What is "user.comment"?

My probable suggestion about where the gpg key's comment field should be written for config --global. Sorry, it's not from ~/.gnupg

JCH> > Is it a correct behaviour? JCH> Yes, matching with user.name/user.email (actually committer information) JCH> is often the most convenient thing to do.

Is it necessary the pgp comment field to be present on the user.name? It isn't for From: in e-mail messages.

JCH> You can use user.signingkey configuration to use a key that doesn't match JCH> your name, too.

Thanks!
73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB  12F8 0CE1 4AAC A0E2 6627)
-- 
http://vereshagin.org
Previous: Junio C Hamano
Message 3 of 3 in “signing tags: user.name assumed to be gpg uid?”
  1. Peter VereshaginDec 29, 2009
  2. Junio C HamanoDec 29, 2009
  3. Peter VereshaginDec 30, 2009

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.