[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 16:02:08 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Jim Meyering <jim <at> 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 other tools (at least one perl module)
> do precisely that, so maybe it's good enough.
>
> If anyone knows of a better way, please tell us.
Should we try:
git config user.signingkey
then fall back to gpgv if that fails to output anything?
At any rate, the general idea of this patch seems great to me.
--
Eric Blake