From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Wed, 20 Mar 2013 20:25:27 GMT
Subject: Re: [BUG?] rebase -i: edit versus unmerged changes
Message-ID: <CALkWK0mgX40oicqxnoa7M3NJP_k8jDrg7mVGyWrg5T+=iRtHQA@mail.gmail.com>
In-Reply-To: <CADeaMWoeRQBbrqLsfieKTE2rRbpzU-Hyp+mv-=CTj+=Znmf=Zw@mail.gmail.com>

Andrew Wong wrote:
> On 3/19/13, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
>> I know that this is expected behavior, but is there an easy way to get
>> rid of this inconsistency?
>
> You can actually rely on "rebase" to run the appropriate command.

Didn't Junio explicitly mention that this is undesirable earlier (from
the point of view of `rebase -i` design)?  The printed advice too,
says that you should use `commit --amend` to finish the job before
invoking --continue.  Also IIRC, we don't allow --continue after
staging changes in the sequencer.