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.
Martijn Laan wrote: > Do you maybe have another idea why this is happening? Unfortunately I > can't find a pattern to when it happens or not. But here's one example: > when I perform a merge, all files that were new on the branch are marked > read only. In the past this did not happen (as I prefer). The read > only-ness is sticky too: it stays both on commit and even on a 'get the > clean copy' (the .# file stays read only which will lead to problems > later when WinCVS wants to rename the file to the .# version a second > time). This sounds more like a WinCVS issue - Try posting on the WinCVS newsgroup. It sounds like you've got the read only checkout flag switched on. Tony