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

Feature request: rebase -i inside of rebase -i

From
GSGeorge Spelvin <lkml@sdf.org>
Date
Mar 20, 2020, 22:30 UTC
Message-ID
<20200320223015.GA19579@SDF.ORG>

I'm cleaning up a patch series for submission, and came across a fixup in patch #4/20 that belongs in #2/20.

Unfortunately, I can't go back two patches to apply the fix until I get to the end of the current rebase, then go back down to clean it up. :-(

Thinking about it, I realized that a rebase in a rebase is a perfectly well defined operation. *If* you don't bother setting a new abort point (it's not a fully nested transaction), *and* require that the tree be clean (no stashing allowed; create a WIP commit instead), it's just a matter of putting some commits back on the front of the todo-list and checking out the old version.

This would make rebase work more like quilt.

I'm not sure how difficult this would be, but it might be worth looking into. (Possibly gated by an extra option like --nested.)

(A second thing that would be nice would be a documented way to break out of a reword and change the commit. A few times I've been improving the documentation of a patch and realized that I should change the function name.)

Next: Junio C Hamano
Message 1 of 25 in “Feature request: rebase -i inside of rebase -i”
  1. George SpelvinMar 20, 2020
  2. Junio C HamanoMar 20, 2020
  3. George SpelvinMar 20, 2020
  4. Johannes SchindelinMar 21, 2020
  5. George SpelvinMar 21, 2020
  6. Johannes SchindelinMar 25, 2020
  7. George SpelvinMar 26, 2020
  8. Johannes SchindelinMar 28, 2020
  9. George SpelvinMar 28, 2020
  10. George SpelvinMar 31, 2020
  11. Philip OakleyMar 31, 2020
  12. Phillip WoodMar 31, 2020
  13. Philip OakleyApr 1, 2020
  14. Phillip WoodApr 7, 2020
  15. Johannes SchindelinApr 4, 2020
  16. Johannes SchindelinApr 4, 2020
  17. George SpelvinApr 4, 2020
  18. Sebastien BruckertApr 6, 2020
  19. George SpelvinApr 6, 2020
  20. Sebastien BruckertApr 7, 2020
  21. George SpelvinApr 7, 2020
  22. Philip OakleyMar 30, 2020
  23. George SpelvinMar 30, 2020
  24. Philip OakleyMar 30, 2020
  25. Johannes SixtMar 21, 2020

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.