From: Philippe Vaucher <philippe.vaucher@gmail.com>
Date: Sat, 14 May 2011 10:58:26 GMT
Subject: Re: git rebase --interactive commits order
Message-ID: <BANLkTinbHOD9AXycM1gXYab+P-PMwOxK6Q@mail.gmail.com>
In-Reply-To: <20110513175112.GA14079@vidovic>

> I don't understand. Why not just _display_ the commit in reverse order?
> Then, from the user POV commands like squash, fixup, etc would apply in
> reverse order too (from up to down); keeping the mental model for "apply
> against ancestor".

Yes, this is what has been suggested. Just display in reverse in the
editor, and on save read the tasks to be done in a reverse manner or
simply reverse the tasks to be done before processing normally.

In fact I can already implement it in my editor by reversing the
commits (vim, some command), doing my stuffs, then reversing it back
before saving. It's pretty error prone because if I forget to reverse
them back then bad things happen, so it'd be nice if rebase handled
this for me.

Philippe