On Wed, Mar 11, 2015 at 12:42 PM, Timur Khanipov <khanipov_at_gmail.com> wrote:
> > if you change the svn:eol-style property to something the file does not
> > have (i.e., the file has CRLF and you set the property to LF), then
>
> I was setting svn:eol-style to 'native' in my experiment. None of the
> files had svn:eol-style previously set.
>
> > svn considers the file contents as modified.
>
> I think this is bad behavior if not a bug. I usually pedantically check
> modifications before committing and if I set svn:eol-style for a bunch of
> files I get nervous when some of them are marked as 'modified (property
> change only)' and some simply as 'modified'. This makes me double check all
> the 'modified' files which is painful. I do not see any reason to mark
> files as 'modified' with the only change being the svn:eol-style property
> value. Could you please give a use case when this behavior is needed?
>
> Please correct me if this issue is related solely to Subversion and not
> TortoiseSVN. In this case I will repost my report to the appropriate
> mailing list.
>
I would be surprised if this was specific to ToroiseSVN but I don't have
the time to debug this for you.
>
> > Once you commit the property
> > change, the line endings in the file are automatically adjusted to what
> > the property says and the file then will show the content status as not
> > modified anymore.
>
> I would also like to point out that it is strange that dubious behavior
> occurs particularly with CRLF files which in fact should have exactly CRLF
> line endings in Windows if svn:eol-style is 'native' and thus should not be
> changed after commit.
>
I'll bet you will find that the on server files are all converted to LF
only when this flag is set and then modified and this is why the difference
is reported but I don't know for sure.
Based on your description this is probably a bug, it should mark the files
with LF only as modified because in essence they are and SVN better modify
them either when the property is set or when it is committed or the working
copy will not be in sync.
And yes, even on Windows, there are reasons for having files with Unix line
endings.
Wayne
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3104602
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-03-11 21:42:28 CET