From: Andy Parkins <andyparkins@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Signed git-tag doesn't find default key
Date: Fri, 20 Oct 2006 20:21:58 +0100 [thread overview]
Message-ID: <200610202021.58157.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610200922170.3962@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
On Friday 2006, October 20 17:32, Linus Torvalds wrote:
> and then do an "adduid", and then add your UID _without_ the "(Google)" in
> there, and that should solve all your problems.
Yeah, obviously that's one way; and while it doesn't really matter to me, it
seems poor form that git doesn't work with gpg as it is. While one could of
course use the "-u" switch, if that is the answer, then why bother with
having the "-s" switch at all?
> You're probably better off with something like
>
> git var GIT_COMMITTER_IDENT | sed 's/\(.*\)<\(.*\)>\(.*\)/\2/'
I've actually settled on:
: ${username:=$(expr "z$tagger" : 'z.*<\(.*\)>')}
In git-tag.sh.
> That said, I've never understood why gpg matches on the comment field.
> Dammit, it _should_ find the key anyway. Stupid program.
I think it's doing the right thing unfortunately. If you search on any part
"Andy Parkins"
"<andyparkins@gmail.com>"
"andyparkins@gmail.com"
"andyparkins"
It finds it fine; the only thing it doesn't find is
"Andy Parkins <andyparkins@gmail.com>"
Which I suppose is fair enough, as it's a fairly specific format to be
searching for.
I'm going to advocate my change of only searching on the email address for
finding the key - there shouldn't be two keys with the same email address
anyway, so there shouldn't be a danger of ambiguity of key. Also, it deals
with the case when someone has entered a different name in git and in their
gpg UID. For example, I would think it shouldn't be a problem that I like to
be called "Andy" on the git list, and yet want my key to say "A. D.
Parkins", "Andrew Parkins" or "Sparky McFly".
Now, I think I've written my name far, far too many times in this email.
Sparky McFly
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-20 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 9:04 Signed git-tag doesn't find default key Andy Parkins
2006-10-20 16:32 ` Linus Torvalds
2006-10-20 19:21 ` Andy Parkins [this message]
2006-10-21 0:52 ` Horst H. von Brand
2006-10-21 7:44 ` Andy Parkins
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=200610202021.58157.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).