From: Brian Ewins <brian.ewins@gmail.com>
To: git@vger.kernel.org
Cc: kusmabite@googlemail.com, Brian Ewins <brian.ewins@gmail.com>
Subject: [PATCH] git-rebase -i: improve usage message
Date: Thu, 29 Oct 2009 00:02:29 +0000 [thread overview]
Message-ID: <1256774549-8191-1-git-send-email-brian.ewins@gmail.com> (raw)
The usage message was confusing as it implied that interactive
mode was optional but the default. Change the message to more
appropriately report usage when the -i flag is supplied.
In addition, use the same division into 3 command formats as
the man page.
Signed-off-by: Brian Ewins <brian.ewins@gmail.com>
---
git-rebase--interactive.sh | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index a1879e3..b988c30 100755
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -12,22 +12,23 @@
OPTIONS_KEEPDASHDASH=
OPTIONS_SPEC="\
-git-rebase [-i] [options] [--] <upstream> [<branch>]
-git-rebase [-i] (--continue | --abort | --skip)
+git rebase -i [options] [--onto <newbase>] [--] <upstream> [<branch>]
+git rebase -i [options] --onto <newbase> --root [--] [<branch>]
+git rebase (--continue | --abort | --skip)
--
Available options are
v,verbose display a diffstat of what changed upstream
onto= rebase onto given branch instead of upstream
p,preserve-merges try to recreate merges instead of ignoring them
s,strategy= use the given merge strategy
-m,merge always used (no-op)
-i,interactive always used (no-op)
+i,interactive interactively edit commits. Implies -m.
+m,merge use merging strategies
+no-verify override pre-rebase hook from stopping the operation
+root rebase all reachable commmits up to the root(s)
Actions:
continue continue rebasing process
abort abort rebasing process and restore original branch
skip skip current patch and continue rebasing process
-no-verify override pre-rebase hook from stopping the operation
-root rebase all reachable commmits up to the root(s)
"
. git-sh-setup
--
1.6.5
next reply other threads:[~2009-10-29 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 0:02 Brian Ewins [this message]
2009-10-29 6:24 ` [PATCH] git-rebase -i: improve usage message Junio C Hamano
2009-10-29 9:40 ` Thomas Rast
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=1256774549-8191-1-git-send-email-brian.ewins@gmail.com \
--to=brian.ewins@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@googlemail.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).