From: Junio C Hamano <gitster@pobox.com>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: git@vger.kernel.org, Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH] format-patch: document --quiet option
Date: Tue, 12 Apr 2011 12:52:22 -0700 [thread overview]
Message-ID: <7v8vvfp7rd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vfwpnp9uf.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 12 Apr 2011 12:07:20 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> @@ -192,6 +192,9 @@ will want to ensure that threading is disabled for `git send-email`.
>> filenames, use specified suffix. A common alternative is
>> `--suffix=.txt`. Leaving this empty will remove the `.patch`
>> suffix.
>> +
>> +--quiet::
>> + Do not print the patch names to standard output.
>
> I see "filenames" in the context and that is "generated filenames".
> ...
Also the existing "Note that ..." that followed your added lines actually
belong to the description of the previous item. Thusly....
-- >8 --
From: Carlos Martín Nieto <cmn@elego.de>
Subject: [PATCH] format-patch: document --quiet option
Signed-off-by: Carlos Martín Nieto <cmn@elego.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
Documentation/git-format-patch.txt | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index a5525e9..f4e959d 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -20,7 +20,7 @@ SYNOPSIS
[--ignore-if-in-upstream]
[--subject-prefix=Subject-Prefix]
[--to=<email>] [--cc=<email>]
- [--cover-letter]
+ [--cover-letter] [--quiet]
[<common diff options>]
[ <since> | <revision range> ]
@@ -196,6 +196,9 @@ will want to ensure that threading is disabled for `git send-email`.
Note that the leading character does not have to be a dot; for example,
you can use `--suffix=-patch` to get `0001-description-of-my-change-patch`.
+--quiet::
+ Do not print the names of the generated files to standard output.
+
--no-binary::
Do not output contents of changes in binary files, instead
display a notice that those files changed. Patches generated
--
1.7.5.rc1.16.g9db19
next prev parent reply other threads:[~2011-04-12 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 21:07 Bug in "git diff --quiet" handling Paul Gortmaker
2011-04-11 21:35 ` Junio C Hamano
2011-04-12 15:51 ` [PATCH] format-patch: document --quiet option Carlos Martín Nieto
2011-04-12 19:07 ` Junio C Hamano
2011-04-12 19:52 ` Junio C Hamano [this message]
2011-04-13 9:29 ` Carlos Martín Nieto
2011-04-12 15:35 ` [PATCH] format-patch: don't pass on the --quiet flag Carlos Martín Nieto
2011-04-12 18:56 ` Junio C Hamano
2011-04-13 9:26 ` Carlos Martín Nieto
2011-04-13 12:10 ` [PATCH] whatchanged: always show the header Carlos Martín Nieto
2011-04-13 15:58 ` Junio C Hamano
2011-04-13 19:38 ` Carlos Martín Nieto
2011-04-14 14:28 ` [PATCH] log: convert to parse-options Carlos Martín Nieto
2011-04-14 17:08 ` Junio C Hamano
2011-04-19 12:33 ` =?UTF-8?q?Carlos=20Mart=C3=ADn=20Nieto?=
2011-04-20 2:38 ` Jeff King
2011-04-20 14:51 ` Carlos Martín Nieto
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=7v8vvfp7rd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=paul.gortmaker@windriver.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).