# [PATCH] config doc: user.signingkey is also used for signed commits

3 messages from 2013-10-14 to 2013-10-14. Participants: Nicolas Vigier, Jonathan Nieder.
Thread: https://gitlist.dev/t/35138

## Nicolas Vigier, 2013-10-14 17:04

Subject: [PATCH] config doc: user.signingkey is also used for signed commits
Message-ID: <1381770276-12062-1-git-send-email-boklm@mars-attacks.org>
URL: https://gitlist.dev/e/1381770276-12062-1-git-send-email-boklm%40mars-attacks.org

```
The description of the user.signingkey option only mentioned its use
when creating a signed tag. Make it clear that is is also used when
creating signed commits.
---
 Documentation/config.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index ec57a15..50c5add 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -2251,11 +2251,11 @@ user.name::
 	environment variables.  See linkgit:git-commit-tree[1].
 
 user.signingkey::
-	If linkgit:git-tag[1] is not selecting the key you want it to
-	automatically when creating a signed tag, you can override the
-	default selection with this variable.  This option is passed
-	unchanged to gpg's --local-user parameter, so you may specify a key
-	using any method that gpg supports.
+	If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the
+	key you want it to automatically when creating a signed tag or
+	commit, you can override the default selection with this variable.
+	This option is passed unchanged to gpg's --local-user parameter,
+	so you may specify a key using any method that gpg supports.
 
 web.browser::
 	Specify a web browser that may be used by some commands.
-- 
1.8.4

```

## Jonathan Nieder, 2013-10-14 17:15

Subject: Re: [PATCH] config doc: user.signingkey is also used for signed commits
Message-ID: <20131014171546.GA12907@google.com>
URL: https://gitlist.dev/e/20131014171546.GA12907%40google.com
In-Reply-To: <1381770276-12062-1-git-send-email-boklm@mars-attacks.org>

```
Nicolas Vigier wrote:

> The description of the user.signingkey option only mentioned its use
> when creating a signed tag. Make it clear that is is also used when
> creating signed commits.
> ---
>  Documentation/config.txt | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

Thanks.  May we have your sign-off?  (See Documentation/SubmittingPatches
section 5 "Sign your work" for what this means.)

```

## Nicolas Vigier, 2013-10-14 17:22

Subject: Re: [PATCH] config doc: user.signingkey is also used for signed commits
Message-ID: <20131014172232.GV4589@mars-attacks.org>
URL: https://gitlist.dev/e/20131014172232.GV4589%40mars-attacks.org
In-Reply-To: <20131014171546.GA12907@google.com>

```
On Mon, 14 Oct 2013, Jonathan Nieder wrote:

> Nicolas Vigier wrote:
> 
> > The description of the user.signingkey option only mentioned its use
> > when creating a signed tag. Make it clear that is is also used when
> > creating signed commits.
> > ---
> >  Documentation/config.txt | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> Thanks.  May we have your sign-off?  (See Documentation/SubmittingPatches
> section 5 "Sign your work" for what this means.)

Oops, I forgot to add it :
Signed-off-by: Nicolas Vigier <boklm@mars-attacks.org>

Thanks

```
