Hello, I did try to find a similar topic in the archive, but couldn't so here I ask. 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. Philippe -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html