On Wed, Dec 13, 2017 at 1:38 AM, Stefan <luke1410_at_posteo.de> wrote:
> On 13/12/2017 01:31, luke1410_at_apache.org wrote:
>> Author: luke1410
>> Date: Wed Dec 13 00:31:56 2017
>> New Revision: 1817969
>> URL: http://svn.apache.org/viewvc?rev=1817969&view=rev
>> * site/staging/docs/release-notes/1.3.html: Remove dead link to tmate.org and
>> only note it in the text as the previously used one.
>> Modified: subversion/site/staging/docs/release-notes/1.3.html
>> URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.3.html?rev=1817969&r1=1817968&r2=1817969&view=diff
>> --- subversion/site/staging/docs/release-notes/1.3.html (original)
>> +++ subversion/site/staging/docs/release-notes/1.3.html Wed Dec 13 00:31:56 2017
>> @@ -434,13 +434,13 @@ working, even with older clients.</p>
>> <p>However, programs that interact with the working copy property
>> files without using the official Subversion APIs or binaries may
>> -experience problems. JavaSVN is
>> -the only project that we know of that falls into this category, and
>> -they have been notified accordingly. If you happen to be using or
>> -developing software that, similarly, bypasses the Subversion APIs,
>> -then you may need to make a minor alteration to the parsing routines.
>> -See revision 16855 of
>> -the Subversion repository for details.</p>
>> +experience problems. JavaSVN (previously available under
>> +http://tmate.org/svn/) is the only project that we know of that falls
>> +into this category, and they have been notified accordingly. If you
>> +happen to be using or developing software that, similarly, bypasses the
>> +Subversion APIs, then you may need to make a minor alteration to the
>> +parsing routines. See <a href="https://svn.apache.org/r856929"
>> +>revision 16855</a> of the Subversion repository for details.</p>
>> </div> <!-- wc-props-change -->
>> </div> <!-- enhancements -->
> The old host pointing to JavaSVN (http://tmate.org/) is no longer valid
> (the page currently advertises the URL being for sale). To prevent
> people accidentally visiting whatever might appear there in the future,
> I thought it might be better to drop the dead link and only note it down
> in the text. Note that as far as I can see JavaSVN no longer exists and
> therefore I couldn't find a replacement for the old link.
> Any objections/alternative suggestions?
TMate Software, that's the company behind SVNKit. See
https://svnkit.com/ (in the footer it says TMate Software). I guess
JavaSVN has become SVNKit sometime later. AFAIK, that's still an
implementation of SVN in pure Java, so it interacts with the
Subversion working copy without going through the Subversion APIs or
binaries. Not sure if we need to point that way from the 1.3 release
notes though (changed names, ... SVNKit obviously doesn't support 1.3
anymore either, ...).
Received on 2017-12-13 09:08:51 CET