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.
Because the software I was using was written to use the commands like that. I have no idea why, I'm a CVS virgin, and what I know about CVS could quite comfortably fit up a gnats nostril ;) It was possibly for cross platform compatibility. Anyway, I did actually manage to work out that command through a lengthy trawl through a manual. I did have a problem getting it to write to a file though, whenever I executed the command it worked fine, but if PHP executed the identical command, it didn't. But I managed to capture the raw output anyway and parse it, and I'm very pleased with the results. Thank you for the suggestion anyway. I didn't know you could use :local:, I had to manually encode the path as part of the command, so I can make thatr 'upgrade'. Cheers. Jay > > I just might have been missing something in your specific scenario that > forbids using regular CVS commands but just out of interest: Why exactly > are you trying to use this complicated way of communicating with the CVS > server (i.e. via the cvs server command) anyway? Why don't you just do > something like: > > cvs -d:local:/Repository rannotate Cinema/Browser.php > temp.txt > > ??? > > I would have thought that sending raw protocol data would only be > required if one was to write his/her own CVS client... > > Cheers, >