Howdy...

The other day, one of the developers got a weird 
message about a specific file revision being locked
by another user. After some hair pulling investigating, 
I found that there was an RCS lock in the ,v file in
the repository. 
I did a cvs admin to unlock the file and all was well.

Then I got to thinking about how I've been looking for 
a way to lock certain files in branches. 

'Twas wondering if anyone's done anything like this.
I mean, I could write a simple Perl script that parses
revision numbers of branches and effectively locks those
revision numbers. Problems would arise, I figger, when 
a file on a branch hasn't been changed, and still has 
the same revision number on various other branches. Alas!

Oh, and why did RCS leave that lock in the file?
Using cvs-1.9 client NT4/Server Solaris 2.x 

Thanks and cheers

Rob

Reply via email to