From: "Mike.lifeguard" <mike.lifeguard@gmail.com>
To: git@vger.kernel.org
Subject: git-tag -s can't find GPG private key
Date: Wed, 27 Jan 2010 17:02:40 -0400 [thread overview]
Message-ID: <4B60A9F0.5000904@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
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. The relevant code would be in
builtin-tag.c.
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAktgqewACgkQst0AR/DaKHuDZgCgpYHD05aJHKF/Wj/uU8CK5swP
SccAoMjHVKM/OZBhbvSvC+aWCQ123Tje
=ZIo0
-----END PGP SIGNATURE-----
next reply other threads:[~2010-01-27 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 21:02 Mike.lifeguard [this message]
2010-01-27 21:06 ` git-tag -s can't find GPG private key Sverre Rabbelier
2010-01-27 21:16 ` Junio C Hamano
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=4B60A9F0.5000904@gmail.com \
--to=mike.lifeguard@gmail.com \
--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