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

[RFH] rebase -i optimization

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Feb 26, 2009, 14:55 UTC
Message-ID
<fabb9a1e0902260655g53fa1e1fg7e4aa76b0f3a80fc@mail.gmail.com>
Heya,

I am currently working on a large set of patches for Melange, and as such I'm using rebase -i a lot to polish things a bit. I do this mainly by 'git rebase -i master' from my topic branch, then change on of the 'pick' lines into an 'edit', and then fix up the commit and 'git rebase --continue'. Now I notice I'm waiting a lot for 'rebase -i' to finish picking the first bunch of commits that I didn't change. Now obviously I couldof done 'git rebase -i <foo>', but then I have first figure out what the last commit I want to change is. Would there be a reason to not reset to the last 'pick' commit instead of to the 'based on' branch (as long as there history is linear)? If so, what would be the best way to go around and implement this?

(to's based on who made the most changes to git-rebase--interactive.sh and cc-ed those involved with git-sequencer)

-- 
Cheers,

Sverre Rabbelier
Next: Johannes Schindelin
Message 1 of 16 in “[RFH] rebase -i optimization”
  1. Sverre RabbelierFeb 26, 2009
  2. Johannes SchindelinFeb 26, 2009
  3. Sverre RabbelierFeb 26, 2009
  4. Johannes SchindelinFeb 27, 2009
  5. Sverre RabbelierFeb 27, 2009
  6. rebase -i: avoid 'git reset' when possibleJohannes Schindelin, Feb 27, 2009
  7. Sverre RabbelierFeb 27, 2009
  8. Johannes SchindelinFeb 27, 2009
  9. Junio C HamanoMar 1, 2009
  10. Johannes SchindelinMar 1, 2009
  11. Junio C HamanoMar 3, 2009
  12. Johannes SchindelinMar 3, 2009
  13. rebase -i: avoid 'git reset' when possibleJohannes Schindelin, Mar 3, 2009
  14. Johannes SixtMar 3, 2009
  15. Johannes SchindelinMar 3, 2009
  16. Sitaram ChamartyFeb 27, 2009

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.