Jim Meyering 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-ta
Eric Blake wrote:
> Jim Meyering meyering.net> writes:
>
>> I've long wanted to avoid hard-coding my GPG key ID
>> in each project's cfg.mk file. The stumbling block was
>> how to derive the key ID from the tag signature.
>> I wanted to avoid relying on the content of gpgv's (gpg --verify's)
>> d
Jim Meyering meyering.net> writes:
> I've long wanted to avoid hard-coding my GPG key ID
> in each project's cfg.mk file. The stumbling block was
> how to derive the key ID from the tag signature.
> I wanted to avoid relying on the content of gpgv's (gpg --verify's)
> diagnostic, but it seems ot
one perl module)
do precisely that, so maybe it's good enough.
If anyone knows of a better way, please tell us.
>From d91a0d2dc678afe8a2c696077f0640e6874f52bc Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Thu, 31 Dec 2009 16:31:11 +0100
Subject: [PATCH] maint.mk: don't require exp
