[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1818496 - /subversion/site/staging/docs/release-notes/1.10.html

From: Evgeny Kotkov <evgeny.kotkov_at_visualsvn.com>
Date: Mon, 18 Dec 2017 01:12:53 +0300

Daniel Shahaf <d.s_at_daniel.shahaf.name> 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
Received on 2017-12-17 23:13:22 CET

This is an archived mail posted to the Subversion Dev mailing list.