Re: eol-style problem

Dave Lawrence wrote:
> 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.

The Subversion guys just added some checks when setting the property.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org