[Gnu-arch-users] [BUG] concurrent library-removes unsafe - locking required

[Julian T. J. Midgley]

Developers working on the same machine cannot share a revision library
entirely without risk, since concurrent library-removes could result
in inconsistencies.  Some locking is needed...

In article <address@hidden>,
Tom Lord  <address@hidden> wrote:
>
>    > From: Robert Collins <address@hidden>
>
>    > On Thu, 2004-04-08 at 14:26, Aaron Bentley wrote:
>
>    >> Concurrent library-remove and get could be problematic, though. :-)
>
>    > rename first, delete second?
>
>There's still the problem that concurrent access to a revision being
>removed can run into problems.   Arch would indeed benefit from a
>little locking protocol in there.
>
>-t

-- 
Julian T. J. Midgley                       http://www.xenoclast.org/
Cambridge, England.
PGP: BCC7863F FP: 52D9 1750 5721 7E58 C9E1  A7D5 3027 2F2E BCC7 863F