Maintaning local changes

[Stephen J. Turnbull]

Ivan Sagalaev writes:

 > May be we're talking about different things then. Today I heard that 
 > Mercurial has something called "patch queues" that I think is what I'm 
 > looking for: a set of changes that are automatically applied on top of 
 > every branch that I'm working locally.

It's not automatically *applied* to branches.  When a branch is
cloned, yes, the patch queue comes with it.  However, the patch queue
both patches and metadata, lives in a particular branch.

Pushing and pulling between repos that have patch queues is
inconvenient, and for practical purposes I don't really see a point
having separate branches when I'm working with a patch queue.  In my
experience, it is much more convenient to use guards on patches, and
use queue operations to change the line of development within the
queue, than to try to coordinate a queue across different branches.

 > It's not another line-of-development within the same project, it
 > lives outside of it.

No, it very much lives within the project.  The patches can be applied
elsewhere as patches, of course, but the automatic management features
apply very much to a specific branch.