All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.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 22:06:00 +0100	[thread overview]
Message-ID: <fabb9a1e1001271306o7e6d9abu1f370ed4698ac055@mail.gmail.com> (raw)
In-Reply-To: <4B60A9F0.5000904@gmail.com>

Heya,

On Wed, Jan 27, 2010 at 22:02, Mike.lifeguard <mike.lifeguard@gmail.com> wrote:
> 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.

It seems you already know where to look, why don't you try and come up
with a patch since it is indeed, your itch to scratch?

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2010-01-27 21:06 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 [this message]
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=fabb9a1e1001271306o7e6d9abu1f370ed4698ac055@mail.gmail.com \
    --to=srabbelier@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.