Re: [PATCH] format-patch: document the format.to configuration setting

From

Jonathan Nieder <jrnieder@gmail.com>

Date

Jul 13, 2010, 06:05 UTC

Message-ID

<20100713060551.GC2425@burratino>

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]'