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 email@example.com.
Here's an idea about a possible solution to the ongoing discussion about the deficiencies of the Reserved Edit mechanism (namely that it could not be sensibly enforced from the server side for individual files or file types): Inspired by the way Tony solved the enforcement of Unix-line endings via the new -kL option, how about handling reserved edits the same way, e.g. by introducing a new kopt -kc. Files with this option set: -would always be checked out read-only, -would always be edited and committed with an implicit -c option, -could still be edited using edit -f. This would allow full fine-grained control on the behaviour while at the same time ensuring that nobody accidentally forgets to use edit -c on these files - very much like -kL ensures that nobody accidentally checks stuff in with Window line endings. Furthermore, adding this as a kopt has the advantage that now the CVSWRAPPERS file could be used to define certain file types as -kc by default. What do you think? Is this feasible? Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)