From: Nils Fenner <nilsfenner@web.de>
To: git@vger.kernel.org
Subject: Commits are no longer gpg-signed in 2.9.0 when "commit.gpgsign" is enabled
Date: Mon, 11 Jul 2016 13:29:10 +0200 [thread overview]
Message-ID: <57838306.5090505@web.de> (raw)
Hey Git community,
since Version 2.9.0, the configuration option "commit.gpgsign" doesn't
work as users would expect. By committing via 'git gui' (or usual 'git
commit' without further option), commits are not being auto-signed any
longer, when "commit.gpgSign" configuration option is set. I also
couldn't find a flag to "workaround" that situation in the GUI. To my
understanding, I now have to pass the '-S' option to 'git commit' every
time and GUI becomes "impractical to use". Surprisingly, nobody seems
having noticed this behavioural change since the release of 2.9.
FYI: In the release log, there's a note stating, that this has been
altered in the context of 'git commit-tree'. Maybe this interferes with
"normal" behaviour.
Would be happy hearing from you soon. Thanks!
Cheers,
Nils
next reply other threads:[~2016-07-11 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:29 Nils Fenner [this message]
2016-07-11 14:44 ` Commits are no longer gpg-signed in 2.9.0 when "commit.gpgsign" is enabled Santiago Torres
2016-07-11 16:27 ` Nils Fenner
2016-07-11 16:51 ` Santiago Torres
2016-07-11 18:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57838306.5090505@web.de \
--to=nilsfenner@web.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).