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

Re: cr, lf on merge ... implement or use gnu diff option?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-11-14 02:00:55 CET

solo turn <soloturn99@yahoo.com> writes:

> is there a chance that subversion will just ommit this by turning it
> around and use a property for the rare case (makefiles)?
>

I don't think Subversion has plans to implement the opposite behavior
(i.e. make 'native' line-endings the automatic default on all files).

When the feature was written, people seemed to not want svn to muck
their data by default, which is what line-translation does. Maybe
people were simply scared. But I've not heard anyone screaming to
reverse the behavior. Maybe people were bitten too many times by CVS.

I think it was part of a general philosophy: "by default, svn will not
tweak your data. If you want that, you must deliberately activate
svn:eol-style or svn:keywords." It's certainly the safest
approach... it just comes at the expense of convenience.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 14 02:02:50 2002

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

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