aboutsummaryrefslogtreecommitdiffstats
path: root/commit.c
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2023-02-15 05:58:34 +0000
committerJunio C Hamano <gitster@pobox.com>2023-02-15 08:55:24 -0800
commitad6b320756d8d9150291c696a02c86d1c2f0f4b2 (patch)
tree1efd328960fdc24c9e74faadbf740d0ccb72e269 /commit.c
parentt7510: add a test case that does not need gpg (diff)
downloadgit-ad6b320756d8d9150291c696a02c86d1c2f0f4b2.tar.gz
git-ad6b320756d8d9150291c696a02c86d1c2f0f4b2.zip
gpg: do show gpg's error message upon failure
There are few things more frustrating when signing a commit fails than reading a terse "error: gpg failed to sign the data" message followed by the unsurprising "fatal: failed to write commit object" message. In many cases where signing a commit or tag fails, `gpg` actually said something helpful, on its stderr, and Git even consumed that, but then keeps mum about it. Teach Git to stop withholding that rather important information. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions