A.J.Mechelynck wrote: >Suresh Govindachar wrote: >> Based on Sir Raorn's reply, I tried: >> >> C:\home\suresh\develop\vim\cvs>c:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim checkout vim7 >> >> which did lots of stuff and ended with: >> >> U vim7/src/xxd/xxd.c >> cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected >> >> Repeating the command resulted in the same message: >> >> cvs checkout: Updating vim7/src/xxd >> cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected >> >> Doing only update as follows: >> >> C:\home\suresh\develop\vim\cvs>c:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim update >> >> resulted in the same message: >> >> cvs update: Updating vim7/src/xxd >> cvs update: dying gasps from vim.cvs.sourceforge.net unexpected >> >> Is this normal? If not, what should I do? > > If CVS is sick, That's my question -- does that message mean cvs is sick or is that message a normal termination message from cvs?
> you can always fall back on good old FTP (or even HTTP): The reason for fetching from cvs is to avoid having to patch. (and the reason for not using svn is that svn is out-of-date, and svn differes from Bram's cvs by CR/LF in some files). --Suresh
