From: Junio C Hamano <gitster@pobox.com>
To: crquan@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-remote: add verbose mode to git remote update
Date: Tue, 18 Nov 2008 17:53:23 -0800 [thread overview]
Message-ID: <7vod0ctrak.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1227006242-21290-1-git-send-email-crquan@gmail.com
crquan@gmail.com writes:
> From: Cheng Renquan <crquan@gmail.com>
>
> Pass the verbose mode parameter to the underlying fetch command.
>
> $ ./git remote -v update
> Updating origin
> From git://git.kernel.org/pub/scm/git/git
> ...
> Signed-off-by: Cheng Renquan <crquan@gmail.com>
> ---
> So now the patch looks very simple.
Indeed it does ;-), but there still is a minor nit.
> + "git remote update [-v | --verbose] [group]",
Notice the difference between the example in your commit log message and
the help text?
I think "git remote [options] [cmd] [more options]" which is the current
option parser seems to try doing is very misguided, and a longer term
fix-up might be to redo the cmd_remote() option parser, but in the short
term, let's apply your patch with the following minor fixup:
diff --git c/builtin-remote.c w/builtin-remote.c
index 0af742b..abc8dd8 100644
--- c/builtin-remote.c
+++ w/builtin-remote.c
@@ -14,7 +14,7 @@ static const char * const builtin_remote_usage[] = {
"git remote rm <name>",
"git remote show [-n] <name>",
"git remote prune [-n | --dry-run] <name>",
- "git remote update [-v | --verbose] [group]",
+ "git remote [-v | --verbose] update [group]",
NULL
};
prev parent reply other threads:[~2008-11-19 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 11:04 [PATCH 2/2] git-remote: add verbose mode to git remote update crquan
2008-11-19 1:53 ` Junio C Hamano [this message]
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=7vod0ctrak.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=crquan@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