X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdevel.texi;h=48ed58d46e2f2a95f654c2431fba02cc5d77b0d5;hb=c10f76f48723b2af78d774d11149032655f1a05c;hp=1aff0655940c6293c7d2adb41205eec7bf41eef7;hpb=8e5950ea4890a031454309cb4a5428ea73266078;p=pintos-anon diff --git a/doc/devel.texi b/doc/devel.texi index 1aff065..48ed58d 100644 --- a/doc/devel.texi +++ b/doc/devel.texi @@ -1,4 +1,4 @@ -@node Development Tools, , Debugging Tools, Top +@node Development Tools @appendix Development Tools Here are some tools that you might find useful while developing code. @@ -49,6 +49,7 @@ home page}. @menu * Setting Up CVS:: * Using CVS:: +* CVS Locking:: @end menu @node Setting Up CVS @@ -188,6 +189,28 @@ ago}. For more information, visit the @uref{https://www.cvshome.org/, , CVS home page}. +@node CVS Locking +@subsection CVS Locking + +You might occasionally see a message like this while using CVS: + +@example +waiting for blp's lock in /afs/ir/users/b/l/blp/cvs +@end example + +This normally means that more than one user is accessing the repository +at the same time. CVS should automatically retry after 30 seconds, at +which time the operation should normally be able to continue. + +If you encounter a long wait for a lock, of more than a minute or so, it +may indicate that a CVS command did not complete properly and failed to +remove its locks. If you think that this is the case, ask the user in +question about it. If it appears that an operation did go awry, then +you (or the named user) can delete files whose names start with +@file{#cvs.rfl}, @file{#cvs.wfl}, or @file{#cvs.lock} in the directory +mentioned in the message. Doing so should allow your operation to +proceed. Do not delete or modify other files. + @node SourceForge @section SourceForge