You're sort of making his point, since Mercurial Queues are about representing revisions as patches rather than snapshots. It's actually a pretty simple idea, j

You're sort of making his point, since Mercurial Queues are about representing revisions as patches rather than snapshots. It's actually a pretty simple idea, just not how Mercurial normally works. That said, the problems with Mercurial Queues come from (1) a bolted-on command-line interface that doesn't fit in with the other hg commands and (2) poor integration with the rest of Mercurial. Which is why for most use cases evolve is considered the better option these days.