Using feature branches to manage packaging with bzr

[Michael Olson]

Michael Olson <mwolson at gnu.org> writes:

> Robert Collins <robertc at robertcollins.net> writes:
>> bzr switch can switch between lightweight working trees. Fixing that
>> for heavyweight checkouts would be relatively easy; and pull
>> --overwrite is essentially the same thing for branches anyhow.
>
> These both still require that separate working trees lie around on the
> disk for each branch somewhere, right?  It doesn't seem like bzr is
> capable of keeping track of all branch information in a single .bzr
                              ^^^^^^^^^^^^^^^^^^^^^^
> directory like git does with its .git directory.  That's a big lose
> for this particular situation, in my opinion.

By "all branch information", I meant "information about all branches,
not just this one".

-- 
       Michael Olson -- FSF Associate Member #652     |
 http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net  |  /` |\ | | |
            Sysadmin -- Hobbies: Lisp, GP2X, HCoop    | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20070807/20e7b9cb/attachment-0001.pgp