On Jul 11 2025, Junio C Hamano wrote:
I think that is correct; I do not think gpg.program is to give a
path to the program, so comparison with core.excludesfile is
probably not so appropriate.
It gives a command line, e.g. "mysign --compat=gnupg",
gpg-interface does not use the shell to run gpg.program, so this won't
work.
$ git config gpg.program "echo --compat=gnupg"
$ git commit -m foo -S
error: cannot run echo --compat=gnupg: No such file or directory
error: gpg failed to sign the data:
(no gpg output)
fatal: failed to write commit object
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."