git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Allow the tag signing key to be specified in the config file
Date: Sat, 27 Jan 2007 14:37:56 +0100	[thread overview]
Message-ID: <45BB55B4.5090303@fs.ei.tum.de> (raw)
In-Reply-To: <7vodolnfes.fsf@assigned-by-dhcp.cox.net>

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

Junio C Hamano wrote:
>> +	: ${keyid:=$(expr "z$tagger" : 'z\(.*>\)')}

is there a reason to use name + email as keyid and not just the email address?  that would also mitigate the need to specify user.sigingkey if only the names missmatch between gpg and git, but the email addresses are the same.

cheers
  simon

-- 
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \


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

  parent reply	other threads:[~2007-01-27 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 14:13 [PATCH] Allow the tag signing key to be specified in the config file Andy Parkins
2007-01-26 16:03 ` Linus Torvalds
2007-01-27  6:37 ` Junio C Hamano
2007-01-27 11:55   ` Andy Parkins
2007-01-27 13:37   ` Simon 'corecode' Schubert [this message]
2007-01-27 16:24     ` Andy Parkins
2007-01-27 16:44       ` Simon 'corecode' Schubert
2007-01-27 22:00 ` 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=45BB55B4.5090303@fs.ei.tum.de \
    --to=corecode@fs.ei.tum.de \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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 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).