From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 3/3] Make rebase--interactive use OPTIONS_SPEC
Date: Fri, 20 Jun 2008 14:15:38 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806201407230.6439@racer> (raw)
In-Reply-To: <1213929935-15093-4-git-send-email-s-beyer@gmx.net>
Hi,
I like the patch. Just a couple comments:
On Fri, 20 Jun 2008, Stephan Beyer wrote:
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index e8ac2ae..aeb9628 100755
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -10,10 +10,25 @@
> # The original idea comes from Eric W. Biederman, in
> # http://article.gmane.org/gmane.comp.version-control.git/22407
>
> -USAGE='(--continue | --abort | --skip | [--preserve-merges] [--first-parent]
> - [--preserve-tags] [--verbose] [--onto <branch>] <upstream> [<branch>])'
> +OPTIONS_KEEPDASHDASH=
> +OPTIONS_SPEC='
> +git-rebase -i [options] <upstream> [<branch>]
> +git-rebase (--continue | --abort | --skip)
Here, "-i" is not an error, but not required either, so it should be
+git-rebase [-i] (--continue | --abort | --skip)
> +--
> +continue Continue rebasing process
> +abort Abort rebasing process and restore original branch
> +skip Skip current patch and continue rebasing process
I wonder if these options (which really should be subcommands) should not
go below the options, for chronological reasons: you are likely to need
the other options before --continue and friends.
> +p,preserve-merges Try to recreate merges instead of ignoring
s/$/ them/
> +t,preserve-tags Update tags to the new commit object
> +m,merge Used anyways (no-op)
> +i,interactive Used anyways (no-op)
s/anyways/always/
Hmm?
> +onto= Rebase onto given branch instead of upstream
> +v,verbose Display a diffstat of what changed upstream
> + When preserving merges:
> +f,first-parent Show only commits following the first parent of each commit
> +s,strategy= Use the given merge strategy
> +'
>
> -OPTIONS_SPEC=
> . git-sh-setup
> require_work_tree
>
> @@ -595,32 +611,36 @@ do
>
> [...]
>
> + --onto)
> + shift
> + ONTO=$(git rev-parse --verify "$1") ||
> + die "Does not point to a valid commit: $1"
> + ;;
You probably need to introduce checks against "git rebase --continue
--onto blabla", then.
> ''|-h)
> usage
> ;;
> - *)
> + --)
> + shift
> + test $# -eq 1 -o $# -eq 2 || usage
I consider this a bugfix. Thanks.
> @@ -720,6 +731,7 @@ EOF
> die_abort "Nothing to do"
>
> output git checkout $ONTO && do_rest
> + exit 0
> ;;
> esac
> shift
This exit is not really necessary, is it? Besides, a simple "exit" would
be more correct: it reuses the exit status of the most recently executed
command, which is what we want here.
Thanks,
Dscho
next prev parent reply other threads:[~2008-06-20 13:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 2:45 some small changes for rebase-i Stephan Beyer
2008-06-20 2:45 ` [PATCH 1/3] t3404: slight improvements Stephan Beyer
2008-06-20 2:45 ` [PATCH 2/3] rebase-i: slight internal improvements Stephan Beyer
2008-06-20 2:45 ` [PATCH 3/3] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 5:48 ` Stephan Beyer
2008-06-20 13:15 ` Johannes Schindelin [this message]
2008-06-20 18:30 ` [PATCH 1/2] t3404: extra checks and s/! git/test_must_fail git/ Stephan Beyer
2008-06-20 18:30 ` [PATCH 2/2] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 18:48 ` [PATCH 1/2] t3404: extra checks and s/! git/test_must_fail git/ Brandon Casey
2008-06-20 19:00 ` Stephan Beyer
2008-06-20 22:18 ` しらいしななこ
2008-06-21 1:46 ` Stephan Beyer
2008-06-21 9:46 ` Junio C Hamano
2008-06-21 23:55 ` [PATCH v3 1/2] t3404: stricter tests for git-rebase--interactive Stephan Beyer
2008-06-21 23:55 ` [PATCH v3 2/2] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 7:16 ` [PATCH 2/3] rebase-i: slight internal improvements Johannes Sixt
2008-06-20 8:01 ` Stephan Beyer
2008-06-20 8:17 ` Johannes Sixt
2008-06-20 12:46 ` Johannes Schindelin
2008-06-20 18:45 ` Stephan Beyer
2008-06-20 13:05 ` [PATCH 1/3] t3404: slight improvements Johannes Schindelin
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=alpine.DEB.1.00.0806201407230.6439@racer \
--to=johannes.schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=s-beyer@gmx.net \
/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