Dale Worley wrote:
>> From: Vincent Starre [mailto:thebitman@comcast.net]
>>
>> The point is: I always want files to be checked out as CRLF(*for
>> example). Once people I have no control over
>> get their hands on these files, they will often come back with CRLF
>> mixed with lone LF's. (often a result of vi
>> being used to make a quick change)
>>
>
>
> If you set svn:eol-style = CRLF, they will never come back with lone LF's
> because these users won't be able to check such a thing in.
>
>
and such is a grave problem.
>
>
>> The point is: when
>> someone's editor mangles a file:
>> 1) this can be easily detected(*svn already does this) and
>> corrected, it would be nice to have this happen on
>> commit rather than requiring it pre-commit.
>> 2) if it can be easily detected and corrected, such
>> corrections can
>> be accounted for and running svn diff should be
>> able to compare these files as they will be comitted
>> (assuming
>> point 1)
>>
>
>
> Any attempt to have Subversion automatically correct such a user mistake
> runs up against a pretty strong philosophical point in Subversion, namely
> that it never *changes* the contents of files, it can only reject a file
> that a user has offered.
>
> Dale
>
>
>
interesting how that isnt remotely true. You are aware of the eol-style
"native", perhaps? When explicitely
told to do so, svn will mangle the line-endings for you. This is not at
all different. The philosophy, as I
understand it, is that SVN will never do things without being told to do
things. Allowing someone to
explicitely say "hey SVN, this thing that I'm stuck doing myself right
now because of your limitations, how
about if you do it yourself from now on?" This (according to the book)
was the very reason eol-style was
included.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 21 02:52:06 2005