> 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 -- 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