Maintaning local changes

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ivan Sagalaev wrote:
> Thanks for the pointers to bzr-loom and bzr-pipeline. I don't have an
> immediate usecase to check them out but I'll keep'em for the future.
> However from the first glance neither looks very convenient. It's a bit
> hard for me to wrap my head around another concept of multiple threads
> along with multiple branches in bzr-loom. And the requirement of
> bzr-pipeline to switch my branches to lightweight-checkout also seems
> too limiting.

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.

> 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.

Aaron

* though admittedly, it doesn't have to be a *lightweight* checkout.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqW7T0ACgkQ0F+nu1YWqI1wRQCghtIuZ4G+5cjM8HUtnTwNxdIK
Q50Anj2EUzlLAkgiNPUxy9yY646Fdmyl
=viEa
-----END PGP SIGNATURE-----