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.
Nice! But if I do this on the server, what do I need to do on the (WinCVS beta 12) client then? I mean, the client thinks it's using pserver, so I guess it will recive a respone it will not understand? -- Christer "Tony Hoyle" <tmh at nodomain.org> wrote in message news:3e71c3b1.249795515 at news.cvsnt.org... > On Fri, 14 Mar 2003 11:42:46 +0100, "Oliver Giesen" <ogware at gmx.net> wrote: > > > >The only commands you will not be able to run from WinCvs are Checkout > >(although this is probably only true for the very first "fresh" checkout), > >Import and Login. If you run these from the command line to create your > >modules and sandboxes you should be able to continue working in WinCvs. Note > >that you will have to configure WinCvs to use the cvs.exe that supports > >:sserver: . I don't think the one that came with WinCvs 1.3.12 already does. > > > You could cheat... > > Use > > [cvsnt] > pserver = sserver_protocol.dll > > as the protocol_map.ini. > > That's if you don't want pserver at all, of course. > > Tony >