On Saturday 03 February 2007 08:30, Frodak wrote:
> --- Les Mikesell <lesmikesell@gmail.com> wrote:
[...]
> > If that were true it wouldn't make any sense to show
> > diffs as lines. If
> > it understands the concept of lines it should know
> > they didn't change.
> > If it doesn't the diffs should only be binary byte
> > differences. What
> > does a line or eol style mean to something that
> > doesn't know about text
> > files?
>
> Subversion can handle a lot of EOL issues. Just try
> it out.
[...]
> This is a LF line
> This is a LF line
> -This is a LF line
> +This is a new CRLF line
> +This is a LF line
> The file source.txt has no properties set and has
> mixed EOLs.
oh, I was hoping to see the '-/+' showing that it detected a change
but did not show what the change was, i.e.
- This eol will change to CRLF
+ This eol will change to CRLF
this is the situation that you are claiming is an excelent idea, but I
don't see why. It simply is contradictory and does not tell me what
changed.
> Now if I merge this into the trunk which has
> svn:eol-style = native it will correctly normalize the
> EOLs in the new files. If I don't have svn:eol-style
> set then it will not normalize the EOLs and the
> working copy will have mixed EOLs.
Now I'm more confused... are you saying svn does modify (normalize)
your mixed eol style when merging? This seems contradictory if
subversion must not be allowed to modify the mixed style text files
upon import.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 20:00:35 2007