All of lore.kernel.org
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Grant Olson <kgo@grant-olson.net>
Cc: git@vger.kernel.org
Subject: Re: PATCH:  Less fragile lookup of gpg key
Date: Sat, 01 May 2010 12:26:03 -0400	[thread overview]
Message-ID: <4BDC561B.4030307@gmail.com> (raw)
In-Reply-To: <4BDC45EB.8090305@grant-olson.net>

Grant Olson wrote:
> When signing a tag, git will attempt to lookup your gpg key if you don't
> provide the key id.  Right now, it's a little fragile.  My gpg key uid
> is "Grant T. Olson (Personal Email) <kgo@grant-olson.net>".  My git user
> info is "Grant T. Olson <kgo@grant-olson.net>".  Things don't match
> because git doesn't have the comment.
> 
> However, if I lookup just by email, things work perfectly.
> 
> I think doing this would make life much easier for new users, and in the
> case that someone has an OpenPGP key without email (e.g. Ubuntu Master
> Signing Key) we can safely assume they're an expert and will either add
> the key id to their configuration or use -u instead of -s.
> 
> Here's a patch that will try to lookup the user by email only if no
> signing key is provided.  If there is no email, it will still fall back
> to the default generated by git.

Why not fall back to just the email if the full lookup fails?

  reply	other threads:[~2010-05-01 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01 15:16 PATCH: Less fragile lookup of gpg key Grant Olson
2010-05-01 16:26 ` A Large Angry SCM [this message]
2010-05-01 17:18   ` Junio C Hamano
2010-05-01 17:25     ` Grant Olson
2010-05-01 19:54       ` Junio C Hamano
2010-05-02 23:39         ` Grant Olson
2010-05-03  0:59         ` Greg A. Woods
2010-05-03  2:09           ` Grant Olson
2010-05-03 11:16           ` Theodore Tso
2010-05-03 22:19             ` Greg A. Woods
2010-05-04  2:19               ` tytso
2010-05-04  2:23                 ` Grant Olson
2010-05-04  6:07                 ` Andreas Ericsson

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=4BDC561B.4030307@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kgo@grant-olson.net \
    /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.