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.
>> With the current version CVS doesn't descend into a repository which >> is different to the one where I have started. > > As far as I know it has never done this... it's not something I've ever > tried though. Basically it can only make one server connection per > client instance, so a root on a different server can't be used - there > are some comments in the source to this effect and it makes sense > (especially given the number of global variables... the effects would be > very unpredictable). Just to make sure that we are talking about the same issue: The 'Root' file in the 'CVS' directory is the difference. In the repository A it contains this value: ':pserver:user at unix:/cvs/cvs-foo' and for the repository B it contains this one: ':pserver:user at unix:/cvs/cvs-bar' With the previous version it worked fine when cvs was using this 'Root' content as the current CVSROOT (like using the 'cvs -d' option). It was implemented in such a way that cvs first walked through all directories belonging to one repository and continued afterwards with the directories of the other repository. This feature got lost and it is also different to the UNIX cvs behaviour. I hope this is different to what you think it is :-) I think the 'bug' is that the latest cvs version does not consider the current 'Root' entry per directory. We need this feature because we have a huge project structure using more than 6 different CVS repository. And I hope that we are not the only one :-). If it helps I can send you a ZIP file with the structure like we're using it or also a trace from the 2.0.41 showing how it descends. Thanks, Werner