git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Henigan <tim.henigan@gmail.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Update 'git remote' usage and man page to match.
Date: Sat, 14 Nov 2009 23:34:00 -0500	[thread overview]
Message-ID: <32c343770911142034j6cf10e36jbd031c49119973c8@mail.gmail.com> (raw)
In-Reply-To: <20091114071948.6117@nanako3.lavabit.com>

On Fri, Nov 13, 2009 at 5:19 PM, Nanako Shiraishi <nanako3@lavabit.com> wrote:
>
> The second change is good but why do you remove -v from the
> synopsis section? Why is it a good idea? Manual pages for
> many other commands list --verbose in their synopsis section.
>

After checking other git operations (fetch, pull, clone, commit, merge, etc)
I found that none of these other commands document '-v' in the synopsis.

With that in mind, I wondered why it had been listed for 'git remote'.  My best
guess is that only some of the 'git remote' subcommands are affected by '-v'.
However, to me it still seems better to only mention it as a general option.
That way if subcommands add/remote support for '-v', the usage string
and man page don't need to be updated.

Please note that even with the change, '-v' is still printed as one of the
general options in the usage string.  I simply removed it from the synopsis
section.

Thank for reviewing,
Tim

  reply	other threads:[~2009-11-15  4:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  1:15 [PATCH] Update 'git remote' usage and man page to match Tim Henigan
2009-11-13 22:19 ` Nanako Shiraishi
2009-11-15  4:34   ` Tim Henigan [this message]
2009-11-15  9:08     ` Junio C Hamano
2009-11-15 19:29       ` Tim Henigan
  -- strict thread matches above, loose matches on Subject: below --
2009-11-12  1:56 Tim Henigan

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=32c343770911142034j6cf10e36jbd031c49119973c8@mail.gmail.com \
    --to=tim.henigan@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@lavabit.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).