I have patches that'll extend 'cvs edit' and 'cvs ci' such that developers can
supply options that'll make these commands abort if others are editting the
files or a valid edit hasn't been taken on the files, respectively. I'll send
you the patches if you want them.
You'll only "need" to use reserved checkouts if your developers refuse to stick
to procedures.
Noel
[EMAIL PROTECTED] on 2001.05.02 06:11:14
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (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:[EMAIL PROTECTED]]
Sent: Wednesday, 2 May 2001 7:23PM
To: Richard Sharp
Cc: '[EMAIL PROTECTED]'
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).
ciao,
hen
Text - character set unknown
