From: Junio C Hamano <gitster@pobox.com>
To: "Mike.lifeguard" <mike.lifeguard@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-tag -s can't find GPG private key
Date: Wed, 27 Jan 2010 13:16:33 -0800 [thread overview]
Message-ID: <7v3a1rp7ta.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4B60A9F0.5000904@gmail.com> (Mike lifeguard's message of "Wed\, 27 Jan 2010 17\:02\:40 -0400")
"Mike.lifeguard" <mike.lifeguard@gmail.com> writes:
> It seems that when the GPG key name and user.name in git's config are
> different, git can't find the appropriate private key to sign the tag.
> Git should attempt to use user.email to find the key. Setting
> user.signingkey is of course a workaround.
user.signingkey was devised for this exact case, and I don't think it is a
work-around.
I do not think "should attempt" is a correct attitude, even though I can
100% agree with "it would have been nicer if it attempted to do this from
day one". You are unfortunately not interacting with git codebase in
early 2005 anymore and there are thousands if not millions of existing
users you should worry about.
Using user.email changes the behaviour for people who do not want a key
that has the same e-mail address, and because the choice of key is all
about security, the logic to choose which one shouldn't be changed
lightly.
prev parent reply other threads:[~2010-01-27 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 21:02 git-tag -s can't find GPG private key Mike.lifeguard
2010-01-27 21:06 ` Sverre Rabbelier
2010-01-27 21:16 ` Junio C Hamano [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=7v3a1rp7ta.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mike.lifeguard@gmail.com \
/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