repository and branch locks in bzr.dev

[Jan Hudec]

On Wed, Feb 01, 2006 at 07:34:23 +1100, Robert Collins wrote:
> 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.

On a related question, how does one lock a file over sftp or even ftp?
Shouldn't it always use lock-files?

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060201/5ffc0782/attachment.pgp