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

Como esta, git?

I notice that after I init and config user.name and user.email the user.comment gets taken from ~/.gpg automatically. Is it a correct behaviour? And, when I try git tag v0.1 -s I get : === gpg: skipped "Peter Vereshagin <peter@vereshagin.org>": secret key not available === and this is because I need to config user.name with the gpg comment: when I === git config --global user.name "Peter Vereshagin (http://vereshagin.org)" === the git tag signs well. But is it a correct behaviour to need the comment as a user's name? On key editing the gpg makes difference between (N)ame and (C)omment by far.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB  12F8 0CE1 4AAC A0E2 6627)

Peter Vereshagin <peter@vereshagin.org> writes:

What is "user.comment"?

Yes, matching with user.name/user.email (actually committer information) is often the most convenient thing to do.

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

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)