Single-user operations getting locked in a shared repository
Aaron Bentley
aaron.bentley at utoronto.ca
Thu Oct 18 13:58:38 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vincent Vertigo wrote:
> I thought the problem might be important enough to be raised on the
> mailing list, as it affects (what i think is) a common operation with
> the latest official release.
No, that's a fairly strange thing to do. If your commit had succeeded,
it would have updated trunk. So why not just work in trunk directly?
It looks like my_work was intended to be a new branch, so "branch" would
be the right command, not "checkout".
If you did work in a checkout, you would normally use a lightweight
checkout, not a heavyweight checkout, because you have low-latency
access to trunk and its repository.
So no, we haven't considered this an important issue, though it would be
nice to fix.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHF1h+0F+nu1YWqI0RAuZSAJ4hiG8plnt52gEAUF4cg2oSKGdC0wCghpo8
VxC/k9e7XBFSV+2m73/J8bA=
=N7F0
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list