lightweight checkouts of readonly branches #39542

[Aaron Bentley]

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

John Arbash Meinel wrote:
> We could update to a new api which wouldn't try to lock the branch
> (lock_only_self_write()). 

This is the approach that Robert suggested recently, and I think it's a
decent approach.

> However, I think it is reasonable to lock the
> Branch when updating the working tree.

I think it's a reasonable default, but I don't think it should be
required.  In the case where you're updating only a working tree, being
able to lock each layer individually makes sense, so that you can
write-lock the tree, but read-lock the branch.

> It might be good to fallback to a
> readonly lock in this instance, though.

I think it would be better as something explicit.

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

iD8DBQFEtAE60F+nu1YWqI0RAqLnAJ0cACgfoeqVjBIUgQKBdag0igh8WQCeL4C2
A56h65YIAvnrrYLcQvACnIQ=
=02Jp
-----END PGP SIGNATURE-----