Author: stefan2
Date: Mon Aug 3 13:10:35 2015
New Revision: 1693898
URL: http://svn.apache.org/r1693898
Log:
In the 1.9 release notes, mention the recently discovered OOD
false positives over HTTPv1.
* publish/docs/release-notes/1.9.html
(#issues): Replace the dummy sub-section with actual contents.
Modified:
subversion/site/publish/docs/release-notes/1.9.html
Modified: subversion/site/publish/docs/release-notes/1.9.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1693898&r1=1693897&r2=1693898&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Mon Aug 3 13:10:35 2015
@@ -1100,15 +1100,25 @@ command can determine the revision in wh
<p>There are some known issues in the Subversion 1.9 releases. These
may be fixed in later 1.9.x releases.</p>
-<div class="h3" id="1234-bad-stuff">
-<h3>### Stuff is broken
- <a class="sectionlink" href="#1234-bad-stuff"
+<div class="h3" id="httpv1-commit-race">
+<h3>"Out of date" errors when committing over HTTPv1
+ <a class="sectionlink" href="#httpv1-commit-race"
title="Link to this section">¶</a>
</h3>
-<p><span style="color: red"><i>### SVN 1.9.0 has broken code in
it.</i></span></p>
+<p>If there are concurrent commits to the same repository, they may
+randomly fail with an "out of date" error message without actually
+being in conflict. The problem presents itself to the user like any
+legitimate out-of-date condition and retrying the commit as usual
+will fix the problem.
+</p>
-</div> <!-- 1234-bad-stuff -->
+<p>This only occurs with pre-1.7 clients or if the server has HTTPv2
+disabled via the <tt>SVNAdvertiseV2Protocol off</tt> option. svnserve
+or local repository access are not effected either.
+</p>
+
+</div> <!-- httpv1-commit-race -->
</div> <!-- issues -->
