Mercurial's patch queues ultimately provide very similar benefits and drawbacks to git rebasing, except that:
1. Patch queues may be version indefinitely, since they are their own Mercurial repository, rather than eventually expiring, like rebased commits in the git reflog; but
2. The above requires you maintain discipline in committing the state of your patch repository
Although the second can be trivially automated, the default behavior--rewriting your patch whenever you issue `hg qrefresh`--is far from optimal.
1. Patch queues may be version indefinitely, since they are their own Mercurial repository, rather than eventually expiring, like rebased commits in the git reflog; but
2. The above requires you maintain discipline in committing the state of your patch repository
Although the second can be trivially automated, the default behavior--rewriting your patch whenever you issue `hg qrefresh`--is far from optimal.