[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Multiple issues related to eol-style, tangently perhaps

From: Vincent Starre <thebitman_at_comcast.net>
Date: 2005-07-21 21:01:09 CEST

Dale Worley wrote:

>I guess I don't see why this is a problem at all. I would expect the users
>to learn rather quickly how to fix the this sort of problem, either by not
>making the mistake to start with, or how to correct it before committing.
The same can be said of the whole CRLF thing in general. However, svn
allows some changes to be made automatically
when you explicitely tell it to- for convenience. This is why we program
things in the first place: "This is so mind-numbingly
repetative, why can't the computer just do it itself? Oh wait: it can"

I understand that a philisophical reason against exists, but to say "The
problem does not exist" is simply not true.

Sussman wrote:
> You're missing a key piece of the svn philosophy: "never lose data".

I disagree with the philisophy that anything should ever protect you
against a choice you have explicitely made. However, I
understand where it comes from. Not wanting to /automatically/ mangle
things makes sense. So how about something like this:

$ svn ci
Commit failed: inconsisent line endings
The file "foo.c" uses both CRLF and LF line-ending styles. The eol-style
for this file has been set to "CRLF".
svn can attempt to correct this for you, but such is not recommended.
WARNING: This can damage your files if used improperly!
see "svn help fix-eol" for more information.
attempt to fix line-endings automatically [y/n/?]:

The only reason is convenience.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 21 21:06:07 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.