From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Baz <brian.ewins@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: possible usability issue in rebase -i?
Date: Tue, 27 Oct 2009 16:50:44 +0100 [thread overview]
Message-ID: <40aa078e0910270850u6ffec41cj372da11d9df533f@mail.gmail.com> (raw)
In-Reply-To: <2faad3050910270817l71394722nda55265ed96722df@mail.gmail.com>
On Tue, Oct 27, 2009 at 4:17 PM, Baz <brian.ewins@gmail.com> wrote:
> I've got a somewhat related minor usability issue with rebase -i. I
> accidentally typed something like 'git rebase -i -z' and got this
> message:
>
> error: unknown switch `z'
> usage: git-rebase [-i] [options] [--] <upstream> [<branch>]
> or: git-rebase [-i] (--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)
>
> The last two lines were the surprise. It suggested to me that '-i' and
> '-m' were now the defaults for git-rebase - which of course they're
> not. A user would not know that this is actually reporting the flags
> that work for git-rebase--interactive, especially since that's not
> what the command calls itself. I wasn't sure about the best approach
> to fixing this - the only comparable commands that pass arbitrary
> flags down to an exec'd program make it clear what program is going to
> be called (usually git merge) and so interpreting errors is easier.
>
> It seems the intent here was to signal that the flags are different
> once a rebase is in progress, but this usage message is shown when
> rebase -i -z is called in any state.
If that is the case, my instinct tells me that this information should
be reflected in the usage-string (instead of the parameter
description). Something like this?
--->8---
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index 23ded48..3ed5f94 100755
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -13,15 +13,15 @@
OPTIONS_KEEPDASHDASH=
OPTIONS_SPEC="\
git-rebase [-i] [options] [--] <upstream> [<branch>]
-git-rebase [-i] (--continue | --abort | --skip)
+git-rebase [-i] [-m] (--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)
+m,merge use merging strategies
+i,interactive interactively edit commits
Actions:
continue continue rebasing process
abort abort rebasing process and restore original branch
--
Erik "kusma" Faye-Lund
next prev parent reply other threads:[~2009-10-27 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 10:13 possible usability issue in rebase -i? Erik Faye-Lund
2009-10-27 12:39 ` [PATCH] rebase -i: more graceful handling of invalid commands Jan Krüger
2009-10-27 14:17 ` Johannes Schindelin
2009-10-27 14:21 ` Thomas Rast
2009-10-27 14:58 ` [PATCH v2] " Jan Krüger
2009-10-28 7:18 ` Junio C Hamano
2009-10-27 15:17 ` possible usability issue in rebase -i? Baz
2009-10-27 15:50 ` Erik Faye-Lund [this message]
2009-10-27 21:05 ` Baz
2009-10-28 12:20 ` Erik Faye-Lund
2009-10-28 14:34 ` Baz
2009-10-28 14:41 ` Erik Faye-Lund
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=40aa078e0910270850u6ffec41cj372da11d9df533f@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=brian.ewins@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.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).