[EMAIL PROTECTED] on 2000.02.21 05:52:36 >>--- Forwarded mail from [EMAIL PROTECTED] >>For example, those wishing hard locks can wrap CVS such that one command can >>checkout (in the CVS sense) or update and lock (ie "cvs edit -c") in one shot. > >This particular scenario is fine for wrappers, because static state can be >gathered while the repository is locked (once, during checkout or update) >and then additional action taken based on that static state. However, there >are actions do not lend themselves to that model (e.g. anything that >specifically operates on the HEAD revision) where wrappers around the >CVS executable will fail without some kind of long transaction mechanism >(i.e., the ability to invoke multiple CVS commands on a static repository, >with the guarantee that no one will modify one of the RCS files that is >of interest to the wrapper). This is true. I've requested a "cvs lock" in the past but haven't seen any work done towards it, although, admittedly, I haven't worked on it either. Noel
