On Mon, Jul 11, 2016 at 9:27 AM, Nils Fenner wrote:
> Hi Santiago,
>
> repeated your test here and actually found something interesting. When
> committing via 'git gui', commits are not being gpg-signed, while firing
> a 'git commit' shows the passphrase dialog and signs the commit correctly.
"gi
On Mon, Jul 11, 2016 at 06:27:57PM +0200, Nils Fenner wrote:
> Hi Santiago,
>
> repeated your test here and actually found something interesting. When
> committing via 'git gui', commits are not being gpg-signed, while firing
> a 'git commit' shows the passphrase dialog and signs the commit correc
Hi Santiago,
repeated your test here and actually found something interesting. When
committing via 'git gui', commits are not being gpg-signed, while firing
a 'git commit' shows the passphrase dialog and signs the commit correctly.
Here's what I did:
git init gpg-signing-test && cd gpg-signing-t
Hi Nils,
I just checked and I have commits made in 2.9 with this option set and I
don't seem to have your issue. Here's what I did:
santiago at ~/test-signing ✔ git init
Initialized empty Git repository in /home/santiago/test-signing/.git/
santiago at ~/test-signing ✔ hub create
U
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
5 matches
Mail list logo
