treeless branches + lightweight co-s or colocated branches

[John Arbash Meinel]

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

On 6/20/2012 11:28 AM, Gour wrote:
> On Wed, 20 Jun 2012 10:09:15 +0200 John Arbash Meinel
> <john at arbash-meinel.com> wrote:
> 
>> It doesn't change the storage format, and the branches and
>> structure is actually backwards compatible. (older bzr can
>> commit/pull/push/etc in a colo setup, it just doesn't know how to
>> switch to individual branches, etc.)
> 
> I discussed it with Jelmer on IRC...the confusion is due to:
> 
> gour at atmarama ~> bzr init -h | grep format -v, --verbose
> Display more information. Branch format: --format=ARG
> Specify a format for this branch. See "help formats".
> --development-colo  The 2a format with experimental support for
> colocated --pack-0.92         Pack-based format used in 1.x
> series.
> 
> which makes me think that using colo branches requires 
> --development-colo storage format.
> 
> It seems, based on the info  I got, that this is not true?
> 
> 
> Sincerely, Gour
> 

You do need to issue some sort of command in order to change the
layout on disk. (create the .branches directory, move the current
branch into that, and change the tree into a checkout of that branch.)

All the pieces are the same disk structures, just how they are laid
out is specific. With a 'known' structure, it is then easier to update
the UI to be more aware of how things are on disk.

John
=:->


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/hm6wACgkQJdeBCYSNAAMH7wCgz+HXL92r9y+pM/eeCFaFzAuv
JzQAn2mtHPzJ8BhvyDLvUv5KfXYg9RjD
=dLsC
-----END PGP SIGNATURE-----