Author: stsp
Date: Wed Mar 6 13:29:30 2019
New Revision: 1854923
URL: http://svn.apache.org/viewvc?rev=1854923&view=rev
Log:
* docs/release-notes/1.12.html
(github-issue): Remove. Issue was resolved by Github end of December 2018.
Modified:
subversion/site/publish/docs/release-notes/1.12.html
Modified: subversion/site/publish/docs/release-notes/1.12.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.12.html?rev=1854923&r1=1854922&r2=1854923&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.12.html (original)
+++ subversion/site/publish/docs/release-notes/1.12.html Wed Mar 6 13:29:30
2019
@@ -333,24 +333,6 @@ patch into their swig-3.0.8 packages.)</
</div> <!-- ruby-swig-issue-602 -->
-<div class="h3" id="github-issue">
-<h3>Github's SVN Bridge server implementation incompatible with SVN 1.12
- <a class="sectionlink" href="#github-issue"
- title="Link to this section">¶</a>
-</h3>
-
-<p>As of November 2018, Subversion 1.12 clients are unable to
-check out repositories from Github. Stricter DAV RFC conformance checks
-were added to SVN 1.12 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.
-</p>
-
-
-</div> <!-- github-issue -->
-
</div> <!-- issues -->
<!-- (This section only makes sense when there are some issues listed in it.)
