From: Thiago Farina <tfransosi@gmail.com>
To: git@vger.kernel.org
Cc: Thiago Farina <tfransosi@gmail.com>
Subject: [PATCH] Update usage string of git-request-pull to match with the version of man help.
Date: Tue, 22 Sep 2009 16:52:19 -0400 [thread overview]
Message-ID: <1253652739-13531-1-git-send-email-tfransosi@gmail.com> (raw)
Signed-off-by: Thiago Farina <tfransosi@gmail.com>
---
git-request-pull.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-request-pull.sh b/git-request-pull.sh
index 630cedd..727c69e 100755
--- a/git-request-pull.sh
+++ b/git-request-pull.sh
@@ -8,7 +8,7 @@ USAGE='<start> <url> [<end>]'
LONG_USAGE='Summarizes the changes between two commits to the standard output,
and includes the given URL in the generated summary.'
SUBDIRECTORY_OK='Yes'
-OPTIONS_SPEC='git request-pull [options] start url [end]
+OPTIONS_SPEC='git request-pull [-p] <start> <url> [<end>]
--
p show patch text as well
'
--
1.6.5.rc1.38.gddf44.dirty
reply other threads:[~2009-09-22 20:52 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=1253652739-13531-1-git-send-email-tfransosi@gmail.com \
--to=tfransosi@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).