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.
I forget the exact version of CVSNT server I'm using, but it is pretty recent and much newer than version 2.5.03.2260. I've got a binary file that never had "cvs watch on" before. I set it as such (using TortoiseCVS-1.9.10) and when I check it out, indeed, the file comes through as read only indicating that there is a watch on it. However, when someone else has an edit on it and then I attempt an edit, it doesn't rebuff my attempt. It switches off the readonly flag. I would have expected it to not switch the readonly flag, since concurrent editing is not possible with binary files because of the lack of merging capabilities. On the contrary, if I check in a file using TortoiseCVS (to a recently created test module), which automatically turns on cvs "watch on" at commit time, if someone else has an edit and I attempt to edit, the readonly flag stays in place. This is what I expect to happen. It disallows me from putting the binary file in a state where I can edit it when someone else is editing. My question is, how do I get the behavior of the latter to apply to the former? Why am I seeing different behavior? Is there some flag I forgot to use when manually applying the watch? Again, I just used "cvs watch on" (actually, just "watch on" via the TortoiseCVS "command" option for the file in question). I'll mention one thing, the former case was a file on a branch and the latter on the HEAD (different modules). I don't know if that makes a difference, but I thought I'd mention it just in case. thanks, Jake