[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] maint.mk: don't require explicit gpg_key_ID in cfg.mk
From: |
Eric Blake |
Subject: |
Re: [PATCH] maint.mk: don't require explicit gpg_key_ID in cfg.mk |
Date: |
Thu, 31 Dec 2009 18:30:58 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Jim Meyering <jim <at> meyering.net> writes:
> > git config user.signingkey
>
> I'd rather not, since there's no guarantee that
> it won't have changed between the tagging operation
> and whenever someone runs the announcement-generating rule.
On the other hand, we should probably kill the (unused) VC-tag rule in
maint.mk; it's use of $(gpg_key_ID) is now circular - how do you sign a tag
using the key of the tag that you just signed? Also, should build-aux/do-
release-commit-and-tag be taught to honor a command-line option and/or inspect
git configuration for determining which key to use, especially now that
maint.mk might not have any record of a preferred key? Or at least document in
its --help how to teach git your preferred key for a given repository?
> I am still hoping there's some obscure gpg option
> that can explicitly extract the key ID from a signature.
Sorry, can't help there.
--
Eric Blake