git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Trillaud <etrillaud@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] git-pull: fix fetch-options.txt to not document --quiet and  --verbose twice in git-pull.txt
Date: Wed, 2 Sep 2009 16:38:26 +0200	[thread overview]
Message-ID: <9f50533b0909020738l153c928auc4ecbadfaceeea5f@mail.gmail.com> (raw)

Hello all!
the current man page of git-pull documents twice the --quiet and
--verbose options. fetch-options.txt and merge-options.txt which both
documents these options.
I choose to "ifndef" the paragraphs in fetch-options.txt because IMHO
they give too much details on the --quiet option (see the patch
below). Of course we could modify merge-options.txt instead (the
--quiet paragraph just says : "operate quietly"), I can provide a
patch if you want.

Best regards

-----------------

git-pull.txt includes fetch-options.txt and merge-options.txt which both
document the --quiet and --verbose parameters. So we supress the
--quiet and --verbose paragraphs if fetch-options.txt is included by
git-pull.txt.

Signed-off-by: Emmanuel Trillaud <etrillaud@gmail.com>
---
 Documentation/fetch-options.txt |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index ea3b1bc..5eb2b0e 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt
@@ -1,3 +1,4 @@
+ifndef::git-pull[]
 -q::
 --quiet::
 	Pass --quiet to git-fetch-pack and silence any other internally
@@ -6,6 +7,7 @@
 -v::
 --verbose::
 	Be verbose.
+endif::git-pull[]

 -a::
 --append::
-- 
1.6.4.2.253.g0b1fac

                 reply	other threads:[~2009-09-02 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9f50533b0909020738l153c928auc4ecbadfaceeea5f@mail.gmail.com \
    --to=etrillaud@gmail.com \
    --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).