Jim writes: > > If one is developing and working with both platforms, his tools better be > able to work with each other's TEXT without difficulty.
No, you just need to learn to use the tools on the platform they were intended for instead of pretending that the two platforms are interchangeable. If there were only two platforms in the world, you might have a point, but there are more text file formats in heaven and earth than are dreamt of in your philosophy. The fact that the DOS and Unix text file formats are similar makes it tempting to pretend that they're the same, or at least can be used interchangably, but the fact remains that they are, in reality, *different* and are *not* interchangeable. > I know I see even more sign of segregation of text and binary in CVS today > than in prior versions... it's really too bad that everyone knows and is > comfortable with CVS... if only they had realized sooner, this mentality > that 'what you checkin is NOT what you checkout' would not have been so > concrete, and this ... would not be an issue. CVS's role in life is to manage source code in a platform independent manner. A DOS file is not useful on an IBM mainframe or on an Alpha running VMS. It may not even be useful on a Unix-like system (some compilers *will* object to the CRs). But a source file using the local text file conventions *is* useful. If you want to get out byte-for- byte what you checked in, then use binary mode; that's what it's for. -Larry Jones They say winning isn't everything, and I've decided to take their word for it. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
