* [PATCH] config doc: user.signingkey is also used for signed commits
@ 2013-10-14 17:04 Nicolas Vigier
2013-10-14 17:15 ` Jonathan Nieder
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Vigier @ 2013-10-14 17:04 UTC (permalink / raw)
To: git; +Cc: Nicolas Vigier
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] config doc: user.signingkey is also used for signed commits
2013-10-14 17:04 [PATCH] config doc: user.signingkey is also used for signed commits Nicolas Vigier
@ 2013-10-14 17:15 ` Jonathan Nieder
2013-10-14 17:22 ` Nicolas Vigier
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Nieder @ 2013-10-14 17:15 UTC (permalink / raw)
To: Nicolas Vigier; +Cc: git
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.)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] config doc: user.signingkey is also used for signed commits
2013-10-14 17:15 ` Jonathan Nieder
@ 2013-10-14 17:22 ` Nicolas Vigier
0 siblings, 0 replies; 3+ messages in thread
From: Nicolas Vigier @ 2013-10-14 17:22 UTC (permalink / raw)
To: Jonathan Nieder; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-10-14 17:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-14 17:04 [PATCH] config doc: user.signingkey is also used for signed commits Nicolas Vigier
2013-10-14 17:15 ` Jonathan Nieder
2013-10-14 17:22 ` Nicolas Vigier
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).