[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: Thu, 3 May 2001 11:59:35 -0400

I don't think you understand.  You need to install the patches.  Have you done

Once the patches are installed, developers must use 'cvs edit -c' and 'cvs ci
-c' (have them all put these options in their .cvsrc files).


|        |                           |
|        |          address@hidden|
|        |       |
|        |                           |
|        |          2001.05.02 22:04 |
|        |                           |
  |                                                                            |
  |       To:     address@hidden, address@hidden                      |
  |       cc:     address@hidden, (bcc: Noel L Yap)               |
  |       Subject:     RE: Reserved checkouts.                                 |

Members Equity Email System
I've tried the "cvs watch on" method but it still allows another user to do
a "cvs edit" ie it does not fail when I've tried to check it out as another
user. Any ideas ?

-----Original Message-----
From: Noel L Yap [mailto:address@hidden
Sent: Thursday, 3 May 2001 2:34AM
To: address@hidden
Cc: address@hidden; address@hidden
Subject: RE: Reserved checkouts.

Let me make things more explicit.  With the patches and 'edit -c' and
-c' in ~/.cvsrc, the work flow would be:
1. Developer checks out module (all files are read only due to 'cvs watch
2. Developer does 'cvs edit'.  If someone else is already editting the file,
'cvs edit' fails and developer should contact other editors before
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.


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

reply via email to

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