svn commit: r1857386 - /subversion/site/staging/docs/release-notes/1.12.html

[stsp]

Author: stsp
Date: Fri Apr 12 09:14:45 2019
New Revision: 1857386

URL: http://svn.apache.org/viewvc?rev=1857386&view=rev
Log:
* staging/docs/release-notes/1.12.html
  (github-issue): remove; no longer relevant

Modified:
    subversion/site/staging/docs/release-notes/1.12.html

Modified: subversion/site/staging/docs/release-notes/1.12.html
URL: 
http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.12.html?rev=1857386&r1=1857385&r2=1857386&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.12.html (original)
+++ subversion/site/staging/docs/release-notes/1.12.html Fri Apr 12 09:14:45 
2019
@@ -468,24 +468,6 @@ This problem affects the <a href="1.10.h
 
 </div>  <!-- apr-1-7 -->
 
-<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">&para;</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.)