On Friday 2006, October 20 17:32, Linus Torvalds wrote:

quoted text
> 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, i=
t=20
seems poor form that git doesn't work with gpg as it is.  While one could o=
f=20
course use the "-u" switch, if that is the answer, then why bother with=20
having the "-s" switch at all?

quoted text
> You're probably better off with something like
>
> 	git var GIT_COMMITTER_IDENT | sed 's/\(.*\)<\(.*\)>\(.*\)//'

I've actually settled on:

: ${username:=3D$(expr "z$tagger" : 'z.*<\(.*\)>')}

In git-tag.sh.

quoted text
> 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=20
searching for.

I'm going to advocate my change of only searching on the email address for=
=20
finding the key - there shouldn't be two keys with the same email address=20
anyway, so there shouldn't be a danger of ambiguity of key.  Also, it deals=
=20
with the case when someone has entered a different name in git and in their=
=20
gpg UID.  For example, I would think it shouldn't be a problem that I like =
to=20
be called "Andy" on the git list, and yet want my key to say "A. D.=20
Parkins", "Andrew Parkins" or "Sparky McFly".=20

Now, I think I've written my name far, far too many times in this email.


Sparky McFly
=2D-=20
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com