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.
Arthur,
Thanks for your quick response.
A test using TortoiseCVS 1.10.7 in conjunction with CVSNT 2.5.04 (build 3125) yields the same result. That is, releasing a read-only file for which no "cvs edit" request had been issued results in the triggering of the temporary unedit watch on the file for another user.
This behaviour did not seem to occur when using TortoiseCVS 1.8.29 with CVSNT 2.5.03 (build 2260). However, on further investigation I discovered that the people using the older version of TortoiseCVS had all failed to put a valid .forward file into their home directory on our unix CVS server. Essentially, the older version does have the same behaviour, but for these users the emails from the triggered unedit watches were never delivered, thus making it look like different behaviour.
I would still like to know if I can prevent the triggering of temporary unedit watches when the CVSNT client is used to release a file that has not been edited. These temporary watches do not get triggered when such a file is released from a working directory on one of our unix machines (using the unix client/server implementation of CVS rather than CVSNT). Do you know if this can be achieved with CVSNT?
Alf.
Arthur Barrett wrote:
> Alf,
>
> I hope OZ is warming up for spring - I've been in Europe enjoying summer for the past few weeks but am returning to Sydney on Friday...
>
>> TortoiseCVS version: 1.10.7
>> CVSNT version: 2.5.03 (build 2382)
>
> That is getting a bit old now - can you try the latest 2.5.04 RC8 on a "test" server and tell us if the problem still occurs?
> http://www.cvsnt.org/wiki/Download
>
> Regards,
>
>
> Arthur Barrett
>
>
--
Alf Pearce
Student System Project Telephone: (03) 8344 2826
Fax: (03) 8344 9493
The University of Melbourne Email: alfp at unimelb.edu.au
Disclaimer: <http://ariel.its.unimelb.edu.au/~alfp/disclaimer/>