From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonas Fonseca <fonseca@diku.dk>, git@vger.kernel.org
Subject: Re: [BUG] git-rebase fails when a commit message contains a diff
Date: Fri, 9 Nov 2007 02:28:15 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711090225110.4362@racer.site> (raw)
In-Reply-To: <7v640cxitc.fsf@gitster.siamese.dyndns.org>
Hi,
On Thu, 8 Nov 2007, Junio C Hamano wrote:
> I wonder if this is a sensible thing to do, regardless of the issue of
> commit log message that contains anything.
>
> The patch replaces git-rebase with git-rebase--interactive. The only
> difference from the existing "git-rebase -i" is if the command is called
> without "-i" the initial "here is the to-do list. please rearrange the
> lines, modify 'pick' to 'edit' or whatever as appropriate" step is done
> without letting the user edit the list.
Hmm. I don't know, really. I had the impression that the "git
format-patch | git am" pipeline would be faster.
But if we were to do this, we'd get a progress meter for free. And bugs
exposed, no doubt.
> Makefile | 2 +-
> git-rebase--interactive.sh => git-rebase.sh | 14 ++++++++++----
> 2 files changed, 11 insertions(+), 5 deletions(-)
What about the existing git-rebase.sh?
> diff --git a/git-rebase--interactive.sh b/git-rebase.sh
> similarity index 98%
> rename from git-rebase--interactive.sh
> rename to git-rebase.sh
> index 76dc679..1dd6f6d 100755
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase.sh
> @@ -346,6 +347,9 @@ do_rest () {
> while test $# != 0
> do
> case "$1" in
> + --interactive|-i)
> + INTERACTIVE=t
> + ;;
There is already a case for that, further down.
> @@ -504,9 +508,11 @@ EOF
> die_abort "Nothing to do"
>
> cp "$TODO" "$TODO".backup
> - git_editor "$TODO" ||
> - die "Could not execute editor"
> -
> + case "$INTERACTIVE" in
> + t)
> + git_editor "$TODO" || die "Could not execute editor"
> + ;;
> + esac
Would that not be easier to read as
test t = "$INTERACTIVE" &&
git_editor "$TODO" || die "Could not execute editor"
Hmm?
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-09 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 1:12 [BUG] git-rebase fails when a commit message contains a diff Jonas Fonseca
2007-11-09 1:39 ` Junio C Hamano
2007-11-09 1:51 ` Junio C Hamano
2007-11-09 2:18 ` Junio C Hamano
2007-11-09 2:28 ` Johannes Schindelin [this message]
2007-11-09 2:37 ` Junio C Hamano
2007-11-09 14:19 ` Johannes Schindelin
2007-11-11 22:31 ` Björn Steinbrink
2007-11-09 7:57 ` Benoit Sigoure
2007-11-09 8:57 ` Johannes Sixt
2007-11-09 9:05 ` Ralf Wildenhues
2007-11-09 9:07 ` Benoit Sigoure
2007-11-09 13:20 ` Johannes Schindelin
2007-11-09 10:29 ` Andreas Ericsson
2007-11-09 7:03 ` Steffen Prohaska
2007-11-09 14:18 ` Johannes Schindelin
2007-11-09 14:29 ` Steffen Prohaska
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=Pine.LNX.4.64.0711090225110.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).