git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Olson <kgo@grant-olson.net>
To: tytso@mit.edu
Cc: The Git Mailing List <git@vger.kernel.org>
Subject: Re: PATCH:  Less fragile lookup of gpg key
Date: Mon, 03 May 2010 22:23:31 -0400	[thread overview]
Message-ID: <4BDF8523.1030202@grant-olson.net> (raw)
In-Reply-To: <20100504021937.GY14986@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

On 5/3/2010 10:19 PM, tytso@mit.edu wrote:
> On Mon, May 03, 2010 at 06:19:17PM -0400, Greg A. Woods wrote:
>> Meanwhile the original problem here appears to me to be that Git
>> effectively encourages use of multiple valid keys that may have the same
>> e-mail address attached to multiple key-IDs.
> 
> Yes, I think that *is* the problem.  If you want to optimize for the
> common case, that's fine, but it's also useful to have a way for users
> to specify in their gitconfig files that a specific KeyID should be
> used if they are signing with a particular e-mail ID.
> 

That's already there:

git config user.signingkey 0xDEADBEEF

-Grant


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

  reply	other threads:[~2010-05-04  2:23 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
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 [this message]
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=4BDF8523.1030202@grant-olson.net \
    --to=kgo@grant-olson.net \
    --cc=git@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).