Re: git rebase --interactive commits order

[David <bouncingcats@gmail.com>]

On 9 May 2011 19:30, Philippe Vaucher <philippe.vaucher@gmail.com> wrote:
>
> Is there an option or would it be possible to make it so that `git
> rebase -i` lists commits in reverse chronological order, like it does
> for `git log` ?
>
> Almost every git commands I use lists events in reverse chronological
> order (reflog, log, gitk) and then you do an interactive rebase and it
> always takes me a second or two to switch mindsets and start reading
> them in chronological order. I asked around and I'm far from being the
> only one who think this is counter-intuitive. I understand there's an
> implementation simplicity reason for it to be that way, and also that
> it is somewhat logical to show the commits to be applied in order, but
> as your mind is trained to read them in reverse chronological order
> with the other commands I'd find it more consistant if rebase also
> followed that.

I agree. I use "rebase -i" a lot, often simultaneously viewing with
gitk, and  I find my work rate is reduced because it is anti-intuitive
to have different tools showing the same information in the opposite
order, especially when squashing commits. I find I have to do a mental
double check before every such operation. Like the OP, I would like to
see "rebase -i" gain the capability to display commits in the same
onscreen-ordering as the other command tools.