From: Jonathan Nieder <jrnieder@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] format-patch: document the format.to configuration setting
Date: Tue, 13 Jul 2010 01:05:51 -0500 [thread overview]
Message-ID: <20100713060551.GC2425@burratino> (raw)
In-Reply-To: <20100712185838.GR31048@genesis.frugalware.org>
Hi Miklos,
Miklos Vajna wrote:
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -886,6 +886,10 @@ format.headers::
> Additional email headers to include in a patch to be submitted
> by mail. See linkgit:git-format-patch[1].
>
> +format.to::
> + Additional "To:" headers to include in a patch to be submitted
> + by mail. See the --to option in linkgit:git-format-patch[1].
> +
> format.cc::
> Additional "Cc:" headers to include in a patch to be submitted
> by mail. See the --cc option in linkgit:git-format-patch[1].
Maybe something like this would make sense on top?
Your patch looks good, of course.
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 877f78d..79d54e5 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -887,12 +887,10 @@ format.headers::
by mail. See linkgit:git-format-patch[1].
format.to::
- Additional "To:" headers to include in a patch to be submitted
- by mail. See the --to option in linkgit:git-format-patch[1].
-
format.cc::
- Additional "Cc:" headers to include in a patch to be submitted
- by mail. See the --cc option in linkgit:git-format-patch[1].
+ Additional recipients to include in a patch to be submitted
+ by mail. See the --to and --cc options in
+ linkgit:git-format-patch[1].
format.subjectprefix::
The default for format-patch is to output files with the '[PATCH]'
--
next prev parent reply other threads:[~2010-07-13 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 18:58 [PATCH] format-patch: document the format.to configuration setting Miklos Vajna
2010-07-13 6:05 ` Jonathan Nieder [this message]
2010-07-13 8:41 ` Miklos Vajna
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=20100713060551.GC2425@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.