Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Last month there was some discussion on the dev list about enforcing reserved edits on a file by file basis (cvs admin -kc). Did this ever get anywhere, and is it likely to get into the 2.0.x builds? Basically I want to ensure that no-one can commit to a file unless they have a reserved edit on it, and so ensure that only one person is editing a file at any one time. This only needs to be enforced on certain files at certain points during the development cycle. For the rest of the time it's ok to have multiple developers working on the same code and handling merges/conflict as they happen. I was going to just make people use commit -c, but having tried it out I have a couple of problems. Firstly it's easy for people to forget to put the -c, so it commits anyway, and secondly they can just do an (not reserved) edit anyway. In fact the only thing the reserved edit seems to stop anyone else doing is another reserved edit. Will the proposed admin -kc help with this, or is there some other way of doing it? Regards, Andy -- Andy Harrison - Platform Software Engineer Anite Telecoms Ltd. 127 Fleet Road, Fleet, Hampshire, GU51 3QN, UK [http://www.anite.com/telecoms] "No matter how bad things seem... nothing could be worse than being used as a towel rail." - A.A. Milne Please note that my email domain has changed from @anitetelecoms.com to @anite.com Registered in England No. 1721900 Registered Office: 353 Buckingham Avenue, Slough, Berkshire SL1 4PF, United Kingdom Scanned for viruses by MessageLabs. The integrity and security of this message cannot be guaranteed. This email is intended for the named recipient only, and may contain confidential information and proprietary material. Any unauthorised use or disclosure is prohibited.