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
