Re: HELP - How to stop line break conversion?

[Laine Stump]

"David L. Martin" <address@hidden> writes:

> Ross,
> 
> > How can we stop WinCVS/cvs/whatever is
> > to blame from converting text files, so that the Windows machine has
> > Unix-style files on?
> >
> 
> Recent WinCVS versions (at least since1.1b8) have the option in
> Admin>>Preferences Global tab of checking out ASCII files with Unix LF.
> Check this box.  Be aware that you may need to do a new checkout since the
> CVS/* administrative files in the working area are also affected by this
> option.

It seems like it would make a lot of sense if the CVS commandline on
all platforms (automatically) understood all different line-ending
conventions in the CVS/* files. Likewise, it would also make a lot of
sense if it checked the existing file during updates/diffs/etc and
converted to whatever line-end convention was already in use for each
(non-binary) file in the working directory (alternately, if that made
anyone uneasy, the line-ending type could be stored in the Entries
file, just like tag info, but that wouldn't be backwards
compatible). For those of us who poke around the same work directory
with both Unix and Windows versions of tools, this would make life
much more convenient.

Of course, if this was all combined with a cvs commandline switch to
force line-end convention on checkout (the default would still be
system-dependent), *AND* if checkin always converted files to
newline-only regardless of platform and workdir convention, life would
be very good indeed. ;-)

(yeah yeah, now go ahead and tell me what a stupid idea this is. I
know how the system works... :-/ )