From: Jonathan Nieder <jrnieder@gmail.com>
To: Nicolas Vigier <boklm@mars-attacks.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] config doc: user.signingkey is also used for signed commits
Date: Mon, 14 Oct 2013 10:15:46 -0700 [thread overview]
Message-ID: <20131014171546.GA12907@google.com> (raw)
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.)
next prev parent reply other threads:[~2013-10-14 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-10-14 17:22 ` Nicolas Vigier
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=20131014171546.GA12907@google.com \
--to=jrnieder@gmail.com \
--cc=boklm@mars-attacks.org \
--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).