What is a safe way of backing up a shared bzr repository
Robert Collins
robertc at robertcollins.net
Mon Nov 19 20:59:34 GMT 2007
On Mon, 2007-11-19 at 15:46 -0500, Aaron Bentley wrote:
> It's rare for us to provide scripts when we can provide commands
> instead. I'm not terribly keen on introducing new commands, as some
> people use the length of the command list as a metric for deciding how
> easy a tool is to use.
I'd go for a hidden command that is well documented.
> Next, scope:
>
> Option 1: lock-and-foo
> This is basically what my script provided. It allows any arbitrary
> command to be run with a locked repository.
>
> Option 2: lock-and-copy
> This folds the copying into part of the script, e.g. with shutil.copytree
>
> Option 3: lock-and-fetch
> This uses the appropriate bzr facilities such as fetch to produce (or
> update) a mirror of the repository. This has the advantage of
> potentially working over remote transports, including the smart server.
> But the remote transport must be listable in order for Bazaar to
> discover branches. This option is typically much slower than the others.
>
> Further thoughts?
I think 3 is the primary use case, and as its backup this is going to
typically be local. If we fold it into a more general command that might
be good in keeping command count down though.
-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20071120/379c0cd6/attachment.pgp
More information about the bazaar
mailing list