What is a safe way of backing up a shared bzr repository

Aaron Bentley aaron.bentley at utoronto.ca
Tue Nov 20 13:04:48 GMT 2007


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

Andrew Cowie wrote:
> On Mon, 2007-11-19 at 23:15 -0500, Aaron Bentley wrote:
>>> I must confess that I like the
>>> term "clone" myself as that is often how I conceive of what I'm doing -
>> I'm not a big fan of this term, as I think it oversells the exactness of
>> the copy ...  "bzr clone" will produce something with a different parent
>> branch, and the presence of a working tree is determined by the target
>> location, not the contents of the source. ... [nor]
>> does it match our internals.  We actually have a "clone"
>> primitive for .bzr directories, but for "branch", we use "sprout", not
>> "clone".


> Can I suggest that perhaps a bit of this make its way into the text of
> `bzr branch --help`? I wouldn't go so far as to call it a bug, but that
> sort of behaviour difference is the sort of thing that can trip people
> up.
> 
> ... or remove the behaviour difference :)

I think you're misunderstanding me.  There's no behavioural difference
between "bzr clone" and "bzr branch".  "clone" is merely an alias.

There are several behavioural differences between "bzr clone" and "cp
- -a", which is why I consider "clone" a poor name.  It makes it sound
exact, and it's not.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQttw0F+nu1YWqI0RAttQAJ0T0mr4RSR4w46t52L+mw0mKX9zGQCgg5E9
1ff+lW+fWrdd1GWVtnhxi1k=
=x2c3
-----END PGP SIGNATURE-----



More information about the bazaar mailing list