repository and branch locks in bzr.dev

[Aaron Bentley]

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

Robert Collins wrote:
> I am thinking that if we share the control_files instance in Branch and
> Repository, we can lock the same file, which would be somewhat more
> compatible with prior bzr versions (currently a Repository that is
> locked without a locked branch will allow concurrent writes into
> the .bzr dir)

It will not allow concurrent repository writes, but it will allow, say,
revision-history to be written.  But older versions of bzr would be able
to do repository writes.

My thought here was to support our existing branches adequately, but to
provide the API that we'll want to have in the future.  An optional
LockableFiles parameter to Repository.__init__() didn't seem like
something we would want to retain, long-term.

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

iD8DBQFD33Q/0F+nu1YWqI0RAgz6AJ0R5P2c7YVQpv1ZCJYvo+T8D8KaCgCdF9jt
SZJXKKT82iC96Zx8NGZrRl0=
=4mwk
-----END PGP SIGNATURE-----