As the subject describes, yesterday I experienced my git client attempting to sign my commits with gpg-key X, when I had specified gpg-key Z as such; `git config user.signinkey <key id of gpg-key Z>`
I am using the email associated with gpg-key X as my `git config user.email`, and not the email that my gpg-client has associated with gpg-key Z. Using `GIT_TRACE=1`, I get output like this; `<snip> trace: run_command: gpg --status-fd=2 -bsau <email associated with gpg-key X>` Does git ignore `git config user.signingkey` when it finds a gpg-key in the local gpg-agent whose email matches `git config author.email`? I'd be grateful for any experience or pointers here. I was really hoping the `GPG_TRACE=1` output show the `gpg --status-fd=2` command to reference the key-id, not the email. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/bbad2da1-9a8b-4347-ae01-968607d127cbn%40googlegroups.com.
