Re: Checkout text files with the Unix LF (Oxa) - from command line

[Larry Jones]

Peter Ring writes:
> 
> The host may or may not be part of the use, and the 
> end-of-record format may or may not be important for the 
> host. For example, I might need to manage configuration 
> files for a multi-OS product. While I have both CR (MacOS), 
> LF (*nix), and CR/LF (CPM/MS-DOS) end-of-record files, 
> my editor (emacs) deals with this transparently, and the 
> OS that holds the sandbox have no use for 2/3 of the files. 
> Why should I need to check out files on a Mac just to do 
> something that might as well be done on Windows or Linux?

You're missing the whole point on the way CVS works.  You don't have
files with specific line endings, you just have text files.  When you
check them out on DOS, they have DOS line endings and you can edit them
or whatever with your DOS tools.  When you check them out on Unix, they
have Unix line endings and you can edit them or whatever with your Unix
tools.  When you check them out on Mac, they have Mac line endings and
you can edit them or whatever with your Mac tools.  When you go to
deploy them, you check them out on the platform you're going to deploy
them on and they get the correct line ending for that platform.

In your philosophy, what would you do with VMS files that have a two
byte binary line length followed by the bytes of the line with a NUL pad
byte if required to make the number of bytes even and no line ending
characters at all?!?  In CVS's philosophy, it just works.

-Larry Jones

Fortunately, that was our plan from the start. -- Calvin