Hang at commit time when using sftp or bzr+ssh

[Aaron Bentley]

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

On 11-12-09 10:56 AM, Stephen AuYeung wrote:
> We have a long running process that will perform all bzr
> operations. I believe that the lock will not be held across
> operations.

You can hold the lock for as long as you're comfortable with the data
becoming stale.

> Will there be cached objects, e.g., the master branch object, that
> can safely stay across locks?

Only something immutable could be cached indefinitely.  Revisions,
committed file versions and signatures are immutable-- they are
associated with unique identifiers rather than locations.

I don't think the master branch is immutable.  It can be changed with
the bind, unbind, switch, reconfigure or configure commands, or by
editing bazaar.conf, locations.conf or the relevant branch.conf.

Given that branches can be deleted, I don't believe any aspect of them
is immutable.

On the other hand, if your long-running process is the sole process
allowed to change the master branch, then perhaps it should hold write
locks on all branches.

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

iEYEARECAAYFAk7iMxYACgkQ0F+nu1YWqI0zaQCfbOhouoskFDS/FycjKJyVcSV3
OEEAnRxtpdYg1qXZRGQYtjhmdgX6LvDD
=w/Zi
-----END PGP SIGNATURE-----