On 2/2/2007 9:08 AM, Les Mikesell wrote:
>
> Given the possible combinations, it is not at all difficult. Generally
> you'd want \r, \n, \r\n, and an oddball \n\r to be equivalent on the way
> in,
Okay, suppose we're on Windows, where the native format says \r\n is an
eol. Treating \r, \n, \r\n to be "equivalent on the way in" means they
all get transformed to \n in the repository, the way \r\n is currently
handled? Then as soon as I checked them out again, they'd all be
converted to \r\n. That was my first option: convert everything to
text. But here you've got a version control system modifying your
files. I don't think that's something it should do. Changing files is
the responsibility of the user. svn should not change files, except in
perfectly reversible ways (the way it currently handles true text files).
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 15:49:46 2007