Author: danielsh Date: Sat Dec 29 12:44:20 2018 New Revision: 1849913 URL: http://svn.apache.org/viewvc?rev=1849913&view=rev Log: * docs/release-notes/1.11.html (#github-issue): Update to say the issue has been resolved.
Modified: subversion/site/publish/docs/release-notes/1.11.html Modified: subversion/site/publish/docs/release-notes/1.11.html URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.11.html?rev=1849913&r1=1849912&r2=1849913&view=diff ============================================================================== --- subversion/site/publish/docs/release-notes/1.11.html (original) +++ subversion/site/publish/docs/release-notes/1.11.html Sat Dec 29 12:44:20 2018 @@ -585,13 +585,12 @@ patch into their swig-3.0.8 packages.)</ <p><a href="https://issues.apache.org/jira/browse/SVN-4789">Issue #4789</a></p> -<p>As of November 2018, Subversion 1.11 clients are unable to +<p>During November 2018 Subversion 1.11 clients were unable to check out repositories from Github. Stricter DAV RFC conformance checks -were added to SVN 1.11 clients, and Github's custom SVN server implementation -happens to not conform to the newly expected behaviour. We are waiting for -Github to resolve the issue at their end. In the meantime, Subversion 1.10, and -perhaps even the <a href="https://git-scm.com">Git version control system</a>, -can be used as a workaround. +had been added to SVN 1.11 clients, and Github's custom SVN server implementation +did not conform to the newly expected behaviour. Github has since fixed the +issues on their end, so all Subversion clients should be able to use Github's +SVN bridge again. </p>