Maintaning local changes

[Ivan Sagalaev]

Aaron Bentley wrote:
> Both tools are ways of working with a list of lines-of-development.
> 
> If you use branches as your lines-of-development, you need to use a
> checkout* in order to switch between them.
> 
> If you don't want to have multiple branches, you can embed multiple
> lines-of-development within a single branch.  That's what loom threads are.
> 
> I don't think other options are conceptually possible.

Uhm.. My understanding of terminology may be lacking so please explain.

I use several branches forked from a central one to work on several 
features. Each one has its own working tree. So I don't use one single 
checkout switching between them. Is this the "other" conceptually 
possible option or is it the same thing that you were talking about?

>> Would such a feature be a good addition to bzr core? I mean:
>>
>>     $ ... hack config.c
>>     $ bzr commit --private
>>     $ bzr push
>>     No revisions to push. 
> 
> Implementing this would require multiple lines-of-development, so either
> threads or lightweight checkouts.

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 another 
line-of-development within the same project, it lives outside of it.