http://subversion.tigris.org/issues/show_bug.cgi?id=4072 http://subversion.tigris.org/issues/show_bug.cgi?id=4070
On Thu, Jan 12, 2012, at 08:39, Andy Levy wrote: > On Thu, Jan 12, 2012 at 07:13, Sven Köhler <sven.koeh...@gmail.com> wrote: > > Hi, > > > > consider the following steps: > > - checkout a file from SVN that has svn:eol-style=CRLF > > - verify that the file has CRLF line endings > > - convert the file to unix line endings using dos2unix, recode, etc. > > - verify that the file has LF line endings > > > > Now you observe the following: > > 1) svn diff shows nothing > > 2) svn status shows nothing > > 3) even after svn update, the LF line endings remain > > > > The only command I have found to actually restore the CRLF line endings > > is svn revert. I'm using subversion 1.6.17. > > > > Isn't the behaviour of subversion kind of odd? I mean, I wouldn't have > > set eol-style to something other than native if the line endings > > wouldn't matter to me. It is expected, that svn diff shows nothing. But > > it's odd that svn status doesn't even inform me that the local file has > > been altered - especially if the line endings of that file matter, I > > kind of depend on subversion to tell me about it. It would be another > > nice feature if subversion would not only ignore the line endings, but > > also restore the proper line endings (according to svn:eol-style) on > > demand (for example during an update). > > When you changed EOL characters, did the file timestamps change? >