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

git rebase --interactive commits order

From
PVPhilippe Vaucher <philippe.vaucher@gmail.com>
Date
May 9, 2011, 09:30 UTC
Message-ID
<BANLkTimX2tupqV464+Re8u06TT+qRmqPuw@mail.gmail.com>
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
Next: David
Message 1 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.