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 firstname.lastname@example.org.
Well I am not sure if that actually worked for me. I was working thru the WinCvs client and while importing the *.tar.gz file I changed the file attributes in the import dialog box to binary, but still the import didn't happen correctly even though CVS used the -W option. I could get it into the database correctly only by adding it as a binary file. Do you think I have done something wrong ? Is there a difference between the -kb option as specified alone and specified inside the -W option (I have never used WinCvs in the command line mode) ? The conclusion that I could derive was that if winCvs didnt recognize the file as binary by itself it isnt possible to import it as a binary file. Am I wrong ? Arvind --- Oliver Giesen <ogware at gmx.net> wrote: > > Thanks a lot Mike, > > I guess I have finally been able to understand the > > problem. The link that u sent was definitely > helpful. > > I guess the only thing the doc doesnt talk about > (or > > doesnt say that explicitly) is the fact that the > CVS > > ignores the -kb option even if specified. > > What it _does_ say however is that you should be > fine if you use the > Import dialog from within WinCvs as this does not > rely on the -kb > option but on the -W option, which will always work. > This is also my > experience. I have never had any problems importing > binary files with > WinCvs. > > Cheers, > > Oliver > ---- ------------------ > JID: ogiesen at jabber.org > ICQ: 18777742 > (http://wwp.icq.com/18777742) > > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com