git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git rebase --interactive commits order

From
PVPhilippe Vaucher <philippe.vaucher@gmail.com>
Date
May 14, 2011, 10:58 UTC
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
Previous: Nicolas SebrechtNext: Junio C Hamano
Message 12 of 14 in “git rebase --interactive commits order”
  1. Philippe VaucherMay 9, 2011
  2. DavidMay 9, 2011
  3. Steven E. HarrisMay 9, 2011
  4. Philippe VaucherMay 10, 2011
  5. Sverre RabbelierMay 10, 2011
  6. Junio C HamanoMay 10, 2011
  7. Richard PetersonMay 11, 2011
  8. Junio C HamanoMay 11, 2011
  9. Richard PetersonMay 11, 2011
  10. Philippe VaucherMay 11, 2011
  11. Nicolas SebrechtMay 13, 2011
  12. Philippe VaucherMay 14, 2011
  13. Junio C HamanoMay 10, 2011
  14. Philippe VaucherMay 10, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.