From: Stins, D. <DR...@Zi...> - 2004-03-14 19:28:49
|
Phil, Yes and no. It has to do with: For example, when it=92s working between a Unix repository and a Windows = or Macintosh working copy, it converts file line endings appropriately for e= ach platform. For example, Unix convention is to use a linefeed (LF) only, whereas Windows expects a carriage return/linefeed (CRLF) sequence at the end of each line. Thus, the files in a working cop= y on a Windows machine have CRLF endings, but the files in a working copy of the same project on= a Unix machine have LF endings (the repository itself is always stored in LF format). And CVS also expand keywords like: $Revision$ Also when these are accidentally created in binaries. This will give problems at any operating system. With best regards, Dick Stins ----- Original Message ----- From: "Daintree" <p.d...@pa...> To: <web...@li...> Sent: Sunday, March 14, 2004 8:13 PM Subject: Re: [Web-erp-developers] CVS binary files .doc, .jpeg, .gif ....= . I take it that this was the issue with nt cvs - I checked out the cvs to another linux machine .... no worries with the images for me. Phil ----- Original Message ----- From: "Stins, Dick" <DR...@Zi...> To: "Web-ERP Developers" <Web...@li...> Sent: Sunday, March 14, 2004 11:09 PM Subject: [Web-erp-developers] CVS binary files .doc, .jpeg, .gif ..... > BlankDear all, > > Please add binary files to cvs conform the instructions below. > > with best regards, > Dick Stins > > CVS will expand on each commit to include the revision number. For example, > it might get expanded to: > $Revision: 1.3 $ > CVS will keep that string up to date as the file is developed. (The various > keyword strings are > documented in Chapters 4 and 11.) > This string expansion is a very useful feature in text files, because i= t > allows you to see the revision > number or other information about a file while you=92re editing it. But= what > if the file is a JPEG image > (with a .JPG extension)? Or a compiled executable program? In those kin= ds of > files, CVS could do > some serious damage if it blundered around expanding any keyword string that > it encountered. In a > binary, such strings can even appear by coincidence. > Therefore, when you add a binary file, you have to tell CVS to turn off both > keyword expansion and > line-ending conversion. To do so, use -kb: > > yarkon$ cvs add -kb filename > yarkon$ cvs ci -m "added blah" filename > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick _______________________________________________ Web-erp-developers mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/web-erp-developers |