On Sat, Apr 02, 2016 at 07:16:12PM -0400, santiago@nyu.edu wrote:
From: Santiago Torres <redacted>
The verify_signed_buffer comand might cause a SIGPIPE signal when the
gpg child process terminates early (due to a bad keyid, for example) and
git tries to write to it afterwards. Previously, ignoring SIGPIPE was
done on the builtin/gpg-verify.c command to avoid this issue. However,
s/gpg-verify/verify-tag/ here, I think.
Other than that, nicely explained.
-Peff