Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) iorsh-linux:~/devel/fontforge/build> git log -n 1 --oneline 2aa98f6a5 (HEAD -> master) Dummy signed commit iorsh-linux:~/devel/fontforge/build> git config log.showSignature true iorsh-linux:~/devel/fontforge/build> git log -n 1 --oneline 2aa98f6a5 (HEAD -> master) gpg: Signature made 17:47:50 2024 ינו 06 ש' IST gpg: using RSA key XXXXXXXXXX gpg: issuer "iorsh@xxxxxxxxxxxxxxxxxxxxx" gpg: Good signature from "Maxim Iorsh <iorsh@xxxxxxxxxxxxxxxxxxxxx>" [ultimate] Dummy signed commit What did you expect to happen? (Expected behavior) When asked for oneliner or any specific format, `git log` shouldn't show signature event when configured. What happened instead? (Actual behavior) `git log` always show signatures with log.showSignature enabled, even for explicit formatting requests. What's different between what you expected and what actually happened? Anything else you want to add: This behavior obviously breaks any script which relies on git log to produce preformatted info about commits. It's also quite rare, becaus e probably very few users set log.showSignature config option. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.34.1 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 compiler info: gnuc: 11.4 libc info: glibc: 2.35 $SHELL (typically, interactive shell): /bin/tcsh [Enabled Hooks]
