[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HELP - How to stop line break conversion?

From: Mike Klinke
Subject: Re: HELP - How to stop line break conversion?
Date: Mon, 23 Oct 2000 13:43:10 -0500

This subject comes up a few times a year and one of the more recent times
was back in March/April. In the archives are the threads:

"Unix version doesn't handle ^M in Entries/Repositories if DOS ver used"

"Unix to Dos filtering"

which contain some of the conversation on this topic.

Regards, Mike Klinke

----- Original Message -----
From: "Laine Stump" <address@hidden>
To: <address@hidden>
Sent: Monday, October 23, 2000 10:38 AM
Subject: Re: HELP - How to stop line break conversion?

| "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
| > CVS/* administrative files in the working area are also affected by
| > 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... :-/ )
| _______________________________________________
| Info-cvs mailing list
| address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]