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 11, 2011, 18:45 UTC
Message-ID
<BANLkTikMo_VLMc2zxezgX_mjCaB8C2LgBw@mail.gmail.com>
In-Reply-To
<7v39klgng7.fsf@alter.siamese.dyndns.org>
> You start 'rebase' (without --reverse); it stops with conflict.  Now what
> should happen when you say 'rebase --reverse --continue' now?  Does it
> error out because you are not allowed to change your mind once you
> started?

I had a long answer explaining it all but Richard beat me to it, and his answer is pretty much exactly what I meant. Rebase wouldn't even change, only the order of which stuffs are displayed in the editor.

Show 8 quoted lines
> I am not saying that these small details cannot be worked out. I am saying
> that you would need to spend a lot of effort to take care of the details
> to avoid making it confusing to the users.  And I am also saying that it
> is not even worth wasting the brainpower spent discussing these in this
> thread, if the only "benefit" resulting from it is to add an option that
> allows some people to have an ordered list of things to do "First I do
> this and then I do that" that has to be read backwards. Why spend extra
> effort only to introduce something confusing?

Well for us it's the current way that is confusing (and probably for a lot of other users too, especially new ones). It's what we suggest that would (imho) make it non-confusing... I'd very much like the "benefit" from this discussion to be a change of default in how rebase -i display commits, but as for some people having it reversed seems to be a strong no-go, it seems the only rational thing we can do is offer a --reverse option so the people used to the current way are happy.

If even adding an option is asking for too much, then we might resort to EDITOR tricks and whatnot. You made me realise I could write a vim script that offers the fonctionality I need without even touching git, but it'd work for me only. I fail to see the problem with adding an option which would simplify the life of many people and isn't invasive for the others.

Philippe
Previous: Richard PetersonNext: Nicolas Sebrecht
Message 10 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.