Hi there.
I've just encountered an "Inconsistent line ending style" error
message for the first time, having enabled autoprops in my subversion
configuration to set the svn:eol-style attribute to "native" for text
based files.
While I understand what the tool is telling me, I don't see why
throwing an error message in this case is desirable.
My interpretation of the svnbook is that when set to native, the line
endings in the file are ignored when committing, and the file is
always stored in a normalised way. If the file does for some reason
contain mixed EOL styles after editing, I wouldn't expect it to be
spat out - I'd expect subversion to do what the book says and accept
the commit, storing the file with normalised line endings. If it's
going to ignore them anyway, why should it matter if they're not
consistent?
I appreciate that this is a subversion issue, not a TortoiseSVN one,
however I do believe it is an issue. It would be great if TortoiseSVN
could provide a neat work around.
There was a post recently pointing out that this error message was not
being displayed by Tortoise in certain circumstances (http://
groups.google.com/group/tortoisesvn/browse_thread/thread/
ef96788745f7fc96/6d37b2abad42b291?lnk=raot&pli=1). That's now been
'fixed', but I'd like to suggest a better solution: give the user a
button to click which will immediately normalise the line endings in
the offending file (perhaps as indicated by its svn:eol-style.) This
would save the user having to find and fix the problem manually,
allowing the commit to succeed.
Any thoughts?
Thanks again for providing an excellent tool1
Best regards,
Richard.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2608160
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-12 16:01:20 CEST