On Fri, 5 May 2006, Peter Toft wrote: > Hi there > > I have a project where I need to use cvs locking, i.e. > "cvs watch FILENAME", so other users will check out files > from the CVSROOT and get the files read-only until the > use "cvs edit FILENAME". I have a problem though which I > have not seen described in the howtos etc. > > Assume the "cvs watch on" scenario above; > * User A and B checks module "bla" with the file "bla/a.txt" > * User A does "cd bla; cvs edit a.txt" > * Now User A is deleted from the system, he goes on vacation, or deletes "bla" > * Now User B has to work on "bla/a.txt" but gets the message from > "cd bla; cvs edit a.txt" that User A is locking the model. > > What is the best (and correct) way to handle this locking situation > if User A cannot ask User B to do "cvs unedit a.txt" or "cvs commit a.txt"??? > > Thanx to the person to help me here!
Thanx to Pablo for the answer: cvs admin -u[rev] filename Peter Toft, Ph.D. [EMAIL PROTECTED] http://pto.linux.dk "First they ignore you, then they ridicule you, then they fight you, then you win." -- Mahatma Gandhi _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
