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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
