On Monday 05 February 2007 11:15, Frodak wrote:
> Simply put,
> subversion is a change control tool. Do you
> understand what that means? It is a tool to
> accurately track changes in a file. When it imports
> the file and trys to normalize the file the EOLs that
> it uses, it needs to be accurate so you can get the
> same file out. At any version. I'd say that it would
> be a piss-poor tool if I imported a file and couldn't
> get it out again. Which is what you are suggesting in
> saying that it's ok for svn "trying to fix it". I
> think you are wrong. I don't think it is OK for svn
> to try to fix it.
I agree that there are some files in which svn should never translate
eol styles (to protect from corruption)
I agree that subversion should not modify any files at import. It's
just that you and Erik are saying that it does "translate" eol when
using svn:eol-style property. Are you not mad about that?
I don't get why you are wasting your resources arguing with me when
you could be attacking subversion developers. You should demand that
they remove the supposedly inappropriate feature from svn that
translates eol characters in a text file. See if that flies.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 23:01:18 2007