inaccessible shared repositories

[Kent Gibson]

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


>
> So I think at minimum, we should warn if the containing repository
> is not usable due to a permission issue.  We could error, but it's
> pretty easy to recover from, so maybe that's all we should do.
>
I'd be happy enough for it to error (with a more informative error
message) - so long as there was a command line option to force the
creation of a standalone repository, say bzr branch --standalone

Hmmm, I actually prefer the command line option.
Say my containing repository is accessible, but I don't want my new
branch to go in there.
With the --standalone option I could force it into a standalone.

Cheers,
Kent.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFdKvGgoxTFTi1P8QRAro2AJwKH57HZpgGhDv+dsKTZkaIxtkhAQCfbKb7
n3s4LufvhorDTkWxjvyrh2I=
=rH8X
-----END PGP SIGNATURE-----