On Tue, Dec 11, 2001 at 09:21:04PM +0100, Roman Neuhauser wrote:
> > To: Roman Neuhauser <neuhauser@mobil.cz>
> > Cc: dev@subversion.tigris.org, Karl Fogel <kfogel@newton.ch.collab.net>
> > From: cmpilato@collab.net
> > Date: 11 Dec 2001 13:44:18 -0600
> > Subject: Re: Poll: do we really need newline conversion?
> >
> > Roman Neuhauser <neuhauser@mobil.cz> writes:
> >
> > > I don't think the issue is notepad displaying LF files as a single
> > > line with some strange hollow squares instead of newlines. But no
> > > EOL conversion could bite you in quite a few situations... IIRC
> > > UltraEdit can be set up to display LF files properly, and convert
> > > them to CRLF when you write them out. Check out, modify a single
> > > line, and commit. Oops, the diff is somewhat longer than
> > > expected...
> >
> > You do recall correctly (I used UltraEdit all the time). However,
> > that's a problem with the how the UltraEdit tool was handled on the
> > source code, not how Subversion handled the versioning/retrieval of
> > such.
>
> My point was that ignoring the EOL problem completely can lead to
> worse problems (from the user POV, I know nil about coding it) than
> it tries to avoid.
> No EOL conversion for "text" files would mean SVN is just the thing
> everybody hates in CVS, just upside down (I'm trying to say that no
> EOL conversion would just like CVS trashing users binary files).
Couldn't we use a svn metadata tag (or whatever it's called) to specify
what we think/want the line endings to be? Then you have to --force (or
change that attribute too) to change the line ending.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
---------------------------------------------------------------------
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