RE: Information about multiple checkouts

[Roberts, Iwan(LIT)]

IMHO I believe that the main problem with CVS is that assuming we replace
"checkout" with "cvs edit" in the statement below, user A marks a file for
edit, user B also marks the file for edit, user A gets a notification that
user B is about to edit the file, but user B is not informed that user A has
previously marked the file for edit, therefore one party is informed, but
not the other.  Is there a way for both parties to be notified ?

I.

-----Original Message-----
From: Thornley, David [mailto:address@hidden
Sent: 24 May 2001 15:29
To: CVS
Subject: RE: Information about multiple checkouts



> -----Original Message-----
> From: Bhavaniprasad Polimetla
> [mailto:address@hidden
> Sent: Thursday, May 24, 2001 7:01 AM
> To: CVS
> Subject: Information about multiple checkouts
> 
> 
> Dear Sir,
> 
> I have the following situation.
> 
> User a checked out file abc.java
> When user b try to check out, it need to tell that user a already
> checked out that file.
> How can I implement it in CVS?
> 
First, exactly what do you mean by checkout?  In some systems, it gives
you a copy of the file and a lock, so that you are the only one
allowed to work on it.  In CVS, it gives you a copy of the files
and allows CVS to manage them (by means of metadata in a CVS
directory).  The assumption in CVS is that everybody who works
on a project will have their own local copy of everything that
concerns them.

The standard way to implement something like lockin in CVS is to
"cvs watch on" and ask developers to use "cvs edit" to unlock files
before changing them.  This is advisory only, and there is no way
to enforce locking, but if your developers will deliberately
bypass your procedures you've got a much worse problem than any
version control system can solve.  In practice, advisory locks
work just as well as hard locks.
 

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs