From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: Stephen Boyd <bebarino@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 4/4] Document negated forms of format-patch --to --cc --add-headers
Date: Mon, 29 Aug 2011 22:10:49 +0200 [thread overview]
Message-ID: <b18a36a42a45dd4147c43d959c64e00b9b17e4ac.1314648438.git.trast@student.ethz.ch> (raw)
In-Reply-To: <bbfb7190ca0125798417f57f4d33b5443257e478.1314648438.git.trast@student.ethz.ch>
The negated forms introduced in c426003 (format-patch: add --no-cc,
--no-to, and --no-add-headers, 2010-03-07) were not documented
anywhere. Add them to the descriptions of the positive forms.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
---
I can't help but notice that the options aren't symmetric:
--no-add-header clears more than just the options added by
--add-header. It's probably too late to change though.
Documentation/git-format-patch.txt | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index d13c9b2..6ea9be7 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -166,15 +166,22 @@ will want to ensure that threading is disabled for `git send-email`.
--to=<email>::
Add a `To:` header to the email headers. This is in addition
to any configured headers, and may be used multiple times.
+ The negated form `--no-to` discards all `To:` headers added so
+ far (from config or command line).
--cc=<email>::
Add a `Cc:` header to the email headers. This is in addition
to any configured headers, and may be used multiple times.
+ The negated form `--no-cc` discards all `Cc:` headers added so
+ far (from config or command line).
--add-header=<header>::
Add an arbitrary header to the email headers. This is in addition
to any configured headers, and may be used multiple times.
- For example, `--add-header="Organization: git-foo"`
+ For example, `--add-header="Organization: git-foo"`.
+ The negated form `--no-add-header` discards *all* (`To:`,
+ `Cc:`, and custom) headers added so far from config or command
+ line.
--cover-letter::
In addition to the patches, generate a cover letter file
--
1.7.7.rc0.370.gdcae57
next prev parent reply other threads:[~2011-08-29 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 20:10 [PATCH 1/4] t4014: check for empty files from git format-patch --stdout Thomas Rast
2011-08-29 20:10 ` [PATCH 2/4] t4014: invoke format-patch with --stdout where intended Thomas Rast
2011-08-29 20:10 ` [PATCH 3/4] t4014: "no-add-headers" is actually called "no-add-header" Thomas Rast
2011-08-29 20:10 ` Thomas Rast [this message]
2011-08-29 22:30 ` [PATCH 1/4] t4014: check for empty files from git format-patch --stdout Junio C Hamano
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=b18a36a42a45dd4147c43d959c64e00b9b17e4ac.1314648438.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).