RE: reserved checkouts in CVS (Was: How well does CVS handle other types of data?)
Can someone add http://sourceforge.net/tracker/index.php?func=detail&aid=422733&group_id=4680&atid=304680 to this page, please? This patch originated from the work done by Eric Griswold and Jim Kingdon but without any of the shortcomings. Thanks, Noel |+---> || | || [EMAIL PROTECTED]| || om | || | || 07/13/2001 | || 04:28 PM | || Please | || respond to | || info-cvs | || | |+---> >| || | To: [EMAIL PROTECTED] | | cc: [EMAIL PROTECTED], (bcc: Noel L Yap) | | Subject: RE: How well does CVS handle other types of data? | >| [ On Friday, July 13, 2001 at 12:19:09 (-0700), Jimmy Rimmer wrote: ] > Subject: RE: How well does CVS handle other types of data? > > Or, you could just use the patch for reserved checkouts: > http://www.cvshome.org/cyclic/cvs/dev-reserve.html No, you can't. That does nothing for branches and merges. It's a hack, not a solution, and it takes away concurrent edits (or at least the expectation they're a usable feature). (It may not even work properly in all situations either, and in any case the resulting patched program cannot literaly be called "CVS".) -- Greg A. Woods +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Reserved checkouts.
I don't think you understand. You need to install the patches. Have you done this? 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). Noel |+---> || | || RSharp@membersequ| || ity.com.au | || | || 2001.05.02 22:04 | || | |+---> >| || | To: [EMAIL PROTECTED], [EMAIL PROTECTED] | | cc: [EMAIL PROTECTED], (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:[EMAIL PROTECTED]] Sent: Thursday, 3 May 2001 2:34AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Reserved checkouts. 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. Noel Text - character set unknown
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:[EMAIL PROTECTED]] Sent: Thursday, 3 May 2001 2:34AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Reserved checkouts. 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. Noel MEMBERS EQUITY PTY LTD ABN 56 070 887 679 This email and any attachments are confidential. If you are not the intended recipient, you must not disclose, distribute, copy or use the information contained in this e-mail or any attachments. If you have received this email in error, please tell us immediately by return email and delete this e-mail and any attachments. This message should not be removed.
RE: Reserved checkouts.
[ On Wednesday, May 2, 2001 at 20:11:14 (+1000), Richard Sharp wrote: ] > 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 ? Then don't use CVS. It is the wrong tool for your needs. -- Greg A. Woods +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Reserved checkouts.
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. 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
Re: Reserved checkouts.
On Wed, May 02, 2001 at 08:11:14PM +1000, Richard Sharp wrote: > 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 ? Mark 'em as binary(*) and they won't be merged. Additionally make use of the edit and watch feature as Henner advised. ... or don't use CVS (Concurrent Versions System). Warm Regards, Matthias (*) http://cvshome.org/docs/manual/cvs_9.html#SEC80 -- Matthias Kranz [EMAIL PROTECTED] http://www.belug.org/~kranz ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Reserved checkouts.
[EMAIL PROTECTED] on 2001.05.02 10:21:54 >What you want is some way of controlling who's working on the >file at any given time, and the CVS way to do that is to set >"cvs watch on" all files that you want to control, and ask >the developers to use "cvs edit" to unlock them. This isn't >strict locking, but rather advisory. Having worked with both, >I can testify that strict locking doesn't stop people from >working simultaneously on a file and blowing away other people's >changes, and advisory locking seems to work as well as strict. I think that advisory locking works better than strict locking since developers are still working within the version control tool rather than circumventing it. >(Noel Yap wrote some patches to put teeth into the watch/edit >process, and these can be found at the RCVS project at Sourceforge, >last I looked. These patches were written against an earlier >version of CVS, so use with caution.) I've updated the patches against cvs-1.11, but they're not as well tested as the ones on SourceForge (since I haven't been using CVS as of late). These new patches haven't been posted on SourceForge (yet) so I'll send them out to those who ask. Anyway, "use with caution" still applies. Noel PS I'm still looking for volunteers to patch the docs and tests so that these patches have a greater chance of making it into the "official" CVS release. -- David H. Thornley Software Engineer at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556 at home: (612)-623-0552 or [EMAIL PROTECTED] or http://www.visi.com/~thornley/david/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Reserved checkouts.
Richard Sharp wrote: > > 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 ? > You don't need reserved checkouts in CVS, for the very simple reason that a CVS checkout is not the same thing as a checkout in a locking system. In a locking system, a checkout typically gets a local copy of the file and locks it; in CVS, a checkout gets a local copy of the file and sets up the metadata for it. What you want is some way of controlling who's working on the file at any given time, and the CVS way to do that is to set "cvs watch on" all files that you want to control, and ask the developers to use "cvs edit" to unlock them. This isn't strict locking, but rather advisory. Having worked with both, I can testify that strict locking doesn't stop people from working simultaneously on a file and blowing away other people's changes, and advisory locking seems to work as well as strict. So, add your binary files with -kb (or use cvs admin to put that on later), make sure there is a "cvs watch on" on all of them, and instruct your developers on the correct procedure. Violation of that procedure should be treated as any other act of sabotage. (Noel Yap wrote some patches to put teeth into the watch/edit process, and these can be found at the RCVS project at Sourceforge, last I looked. These patches were written against an earlier version of CVS, so use with caution.) -- David H. Thornley Software Engineer at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556 at home: (612)-623-0552 or [EMAIL PROTECTED] or http://www.visi.com/~thornley/david/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Reserved checkouts.
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
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 MEMBERS EQUITY PTY LTD ABN 56 070 887 679 This email and any attachments are confidential. If you are not the intended recipient, you must not disclose, distribute, copy or use the information contained in this e-mail or any attachments. If you have received this email in error, please tell us immediately by return email and delete this e-mail and any attachments. This message should not be removed.
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 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
