Daniel Shahaf <[email protected]> writes: > This language implies that we made a backwards incompatible change in 1.6, > which is not precisely the case; 1.6 simply started enforcing an API > requirement that 1.5 did not. > > Could we perhaps rephrase this accordingly? I.e., point out that we weren't > inventing a backwards-incompatible requirement, but starting to enforce one > that had always been there?
I would think that from the standpoint of a user reading the release notes, both versions look more or less the same (maybe, with the second one being slightly harder to parse due to its verbosity): Such property line endings were accepted by older servers and can be found in repository dumps, but are considered invalid starting with Subversion 1.6. Such invalid line endings were accepted by older servers and can be found in repository dumps of older repositories, but are rejected by Subversion 1.6 and later. But, presumably, both variants are fine, as both of them explain the reason behind the "Cannot accept non-LF line endings" error — so please feel free to commit this tweak if you think it would be more appropriate. Thanks, Evgeny Kotkov
