From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 30 Jun 2015 17:09:38 GMT
Subject: Re: [PATCH 0/3] rebase -i: drop, missing commits and static checks
Message-ID: <xmqqmvzh6s31.fsf@gitster.dls.corp.google.com>
In-Reply-To: <vpqy4j12knh.fsf@anie.imag.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> There's an alternative:
>
> $ git rebase --edit-todo
> # Make mistakes, save and quit
> Your todo-list has the following issues:
> - ...
> Do you want to edit again (no aborts the rebase) [Y/n]?
>
> There's a precedent with the 'e' command of "git add -p". I have a
> slight preference for non-interactive commands so I prefer not going
> this way though.

edit-todo (and "rebase -i" in general) is all about going
interactive, isn't it?  I was almost going to suggest to keep
spawning the editor until the user gets it right, but that would
infinitely repeat when GIT_EDITOR is set to a broken script, so
I didn't ;-).