On Thu, 2001-12-13 at 11:46, Bruce Atherton wrote:
> At 12:17 AM 12/13/2001 -0500, Greg Hudson wrote:
> >Fine. Linus creates the file, with the "VEC\n" contents, William checks
> >it out, getting "VEC\r\n", the graphics program doesn't bomb on it, he
> >makes the engine design, checks it in, and loses his data.
>
> Ahh, but William gets the same file with your proposal as well. As I've
> said, if you go to multiple platforms without setting the property
> correctly, both proposals will corrupt the file. They just do so in
> different ways.
Yes, but in my scheme William doesn't lose his engine design. (It will
be corrupted on the next checkout, but it's still sitting there
uncorrupted in the repository.)
> >There are special files which want to use CRLF endings even when you check
> >them out on Unix, because they only get used by Windows tools which
> >require CRLF. (Why are they being used on Windows if they're being
> >checked out on Unix? Because we make tarballs out of Unix checkouts.)
>
> Right. But if you don't want the files to have their line endings
> converted, set the line-ending-style to "none". No need to specify what
> specific line endings are actually in the file.
I believe we specifically want to be able to edit these files on Unix
and ensure that any LF line endings which crop up be converted to CRLF.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006