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 firstname.lastname@example.org.
Oliver Giesen wrote: > Well, so what? Use the -kc flag then. It's even more transparent. You could > see the flag when you do a status or even in the WinCvs UI. When you also > see that the file is edited, you can be sure it is being edited by you only > (unless somebody messed with the file attributes but I don't think that > counts...). ..or even -kx (which some might have noticed is almost exactly the same as -kc, except what gets recorded on the server side). There really isn't a huge difference between edit -c and edit -x, except edit -x is enforced so you can't override it by doing an ordinary edit. The -k options are expressions of that (they just trigger default behaviour in certain commands). Having the knowledge of exclusive edits on the server side will be useful in the future, when a lot of the backend reporting stuff gets written (and definately for some of the really funky stuff that's on the horizon). For now as far as most users are concerned it's one more way to do the same thing - with perhaps the added comfort of being called 'exclusive'. At one time I'd have said to someone who wanted exclusive edits 'use another tool'. Now that cvsnt pays for my lunch I've not really got the luxury of doing that... however I'll always focus on the concurrent stuff as that's what I use daily. Tony