"git rebase --interactive" can certainly be used instead of patch queues if you're careful not to mess with published changesets. Mercurial has the histedit ex

"git rebase --interactive" can certainly be used instead of patch queues if you're careful not to mess with published changesets. Mercurial has the histedit extension[1] which does the same thing. The one thing rebase -i and histedit can't really duplicate is versioned patch queues. If you want to keep track of changes to patches over time then rewriting history won't help you. Perhaps you have a big feature with a bunch of moving parts that you want to refine as you get feedback/code review. With versioned queues your colleagues can see what parts of your patches changed since the last time they reviewed them, instead of looking at the entire set of patches as a whole. [1]: http://mercurial.selenic.com/wiki/HisteditExtension http://mercurial.selenic.com/wiki/HisteditExtension