[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Reserved checkouts.

From: Noel L Yap
Subject: RE: Reserved checkouts.
Date: Wed, 2 May 2001 12:34:10 -0400

Let me make things more explicit.  With the patches and 'edit -c' and 'checkin
-c' in ~/.cvsrc, the work flow would be:
1. Developer checks out module (all files are read only due to 'cvs watch on').
2. Developer does 'cvs edit'.  If someone else is already editting the file,
'cvs edit' fails and developer should contact other editors before proceeding.
If it's deemed OK to proceed, developer does 'cvs edit -f'.
3. Everything else is as it was before.

Also, notification should be turned on in case the developer doesn't contact
other editors for any reason.


address@hidden on 2001.05.02 06:11:14

To:   address@hidden
cc:   address@hidden (bcc: Noel L Yap)
Subject:  RE: Reserved checkouts.

Members Equity Email System
But I do need to use reserved checkouts - I have examined the issues for and
against and have decided on reserved checkouts. Some of our files will not
be able to be merged as they are graphic files etc. Any ideas ?

-----Original Message-----
From: Henner Zeller [mailto:address@hidden
Sent: Wednesday, 2 May 2001 7:23PM
To: Richard Sharp
Cc: 'address@hidden'
Subject: Re: Reserved checkouts.

Don't use reserved checkouts -- they should be buried in Software
Configuration Management history. As such, they are not actively supported
by CVS.

If you want to have something similar, but much more flexible (locking +
still the possibility to edit it by others with automatic notification of
the holder of the lock), use the 'watches' supported by CVS (and read the
Cederqvist manual and get some ideas why you probably don't want to use
reserved checkouts).


Attachment: InterScan_Disclaimer.txt
Description: Text - character set unknown

reply via email to

[Prev in Thread] Current Thread [Next in Thread]