git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Henigan <tim.henigan@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, finnag@pvv.org
Cc: git@vger.kernel.org, Nanako Shiraishi <nanako3@lavabit.com>
Subject: [PATCH v2] Update 'git remote update' usage string to match man page.
Date: Sun, 15 Nov 2009 14:46:25 -0500	[thread overview]
Message-ID: <32c343770911151146m82ac4a3p12ecc988da88ab6b@mail.gmail.com> (raw)

Commit b344e161 taught 'git remote update' to understand
[group | remote] as its argument.  The man page was updated
to document this change, but the usage string was not.

Signed-off-by: Tim Henigan <tim.henigan@gmail.com>
---

This updates the patch found at:
http://article.gmane.org/gmane.comp.version-control.git/132953

The change to the man page synopsis has been dropped.  This
patch now only updates the usage string in builtin-remote.c.

The author of commit b344e161 has been added to the CC list.

Based on advice from Junio, further changes to the usage string
and man pages will be explored in a separate patch series.


 builtin-remote.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/builtin-remote.c b/builtin-remote.c
index 0777dd7..c4edb86 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -15,7 +15,7 @@ static const char * const builtin_remote_usage[] = {
 	"git remote set-head <name> [-a | -d | <branch>]",
 	"git remote show [-n] <name>",
 	"git remote prune [-n | --dry-run] <name>",
-	"git remote [-v | --verbose] update [-p | --prune] [group]",
+	"git remote [-v | --verbose] update [-p | --prune] [group | remote]",
 	NULL
 };

-- 
1.6.5.2.185.gb7fba.dirty

             reply	other threads:[~2009-11-15 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 19:46 Tim Henigan [this message]
2009-11-15 21:04 ` [PATCH v2] Update 'git remote update' usage string to match man page 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=32c343770911151146m82ac4a3p12ecc988da88ab6b@mail.gmail.com \
    --to=tim.henigan@gmail.com \
    --cc=finnag@pvv.org \
    --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).