From: SASh-4 <alexiev@gmail.com>
To: git@vger.kernel.org
Subject: Re: "secret key not available". "unable to sign the tag".
Date: Thu, 4 Feb 2010 03:44:44 -0800 (PST) [thread overview]
Message-ID: <1265283884656-4512970.post@n2.nabble.com> (raw)
In-Reply-To: <86367.3986.qm@web37907.mail.mud.yahoo.com>
I had the same problem. Turned out that the user.name must also match the one
in the gpg! Hope this helps!
--
View this message in context: http://n2.nabble.com/secret-key-not-available-unable-to-sign-the-tag-tp1500685p4512970.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-02-04 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:28 "secret key not available". "unable to sign the tag" Gary Yang
2008-11-15 3:57 ` Jeff King
2008-11-17 0:16 ` Linus Torvalds
2008-11-18 16:55 ` Gary Yang
2008-11-18 16:57 ` Gary Yang
2008-11-18 1:59 ` Gary Yang
2008-11-18 4:21 ` Linus Torvalds
2008-11-18 20:22 ` Gary Yang
2008-11-18 20:26 ` Gary Yang
2008-11-18 21:20 ` Gary Yang
2008-11-19 15:42 ` Linus Torvalds
2008-11-19 16:54 ` Gary Yang
2010-02-04 11:44 ` SASh-4 [this message]
[not found] <49236F67.6080807@pcharlan.com>
2008-11-19 2:19 ` Gary Yang
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=1265283884656-4512970.post@n2.nabble.com \
--to=alexiev@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;
as well as URLs for NNTP newsgroup(s).