eol-style problem

A while ago I erroneously added a svn:eol-style property to a file
without giving it a value.

Tortoise helpfully suggests valid eol-styles but doesn't reject invalid
ones.

When somebody went to switch from trunk to a tag (the tag did not have
the property), SVN failed at the point that it tried to remove the
property from their working copy (the error was something like "invalid
eol-style"). So I removed this property from trunk, got the user to
manually remove the property from their working copy and then they could
switch successfully (the property is just merged away at that point).

But then things got much worse. Now anyone on trunk who tries to update
  to the head revision is faced with the same error. The work-around of
course is that they must all manually delete this property.

Now I notice that TSVN does do some sort of sanity checking on
properties, (as indicated by the fact that the svn:executable property
cannot be given a value), so therefore I would suggest that an
improvement here would be that the eol-style is also checked for valid
values.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Dec 7 16:54:15 2007