repository and branch locks in bzr.dev

[Robert Collins]

On Tue, 2006-01-31 at 09:29 -0500, Aaron Bentley wrote:
> -----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.

Well, 0.7 locks branch-format, .dev locks README. So both a 0.7 and
a .dev client can think they have locked the repo files - weaves etc -
and one could be doing a push while the other does a commit, or even two
pushes.

> 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.

I'll have a play and see how it looks... I think I can do it in such a
way we aren't stuck with it inappropriately.

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/20060201/e96c6e52/attachment.pgp