subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@apache.org
Subject svn commit: r1693915 - /subversion/site/publish/docs/release-notes/1.9.html
Date Mon, 03 Aug 2015 15:19:04 GMT
Author: stefan2
Date: Mon Aug  3 15:19:04 2015
New Revision: 1693915

URL: http://svn.apache.org/r1693915
Log:
Polishing the 1.9 release notes bits that I added today.

* publish/docs/release-notes/1.9.html
  (#fewer-ood-conditions): Fix typos & grammar.
  (#rate-limiting-svnserve): Be more explicit about platform-specifics.
  (#httpv1-commit-race): Be more clear about the trigger conditions
                         and how to work around the issue.

Suggested by: danielsh

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=1693915&r1=1693914&r2=1693915&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Mon Aug  3 15:19:04 2015
@@ -847,7 +847,7 @@ command.</p>
      title="Link to this section">&para;</a>
 </h4>
 
-<p>Out best practices suggest that projects should branch and merge
+<p>Our best practices suggest that projects should branch and merge
 at the project root level.  Each merge will then usually change the
 <tt>svn:mergeinfo</tt> property at the project base folder.  To commit
 that change, pre-1.9 servers require the client to have the latest
@@ -862,7 +862,7 @@ got through and the merge commit is reje
 old revisions as long as the directory contents itself did no change.
 Directory contents changes would either be property changes,  added or
 removed entries.  Sub-tree or file contents changes no longer prevent
-the property change to go through.  Of course, true file and tree
+the property change from going through.  Of course, true file and tree
 change conflicts will still result in out-of-date errors.
 </p>
 
@@ -885,8 +885,7 @@ connection - potentially consuming a lar
 Subversion 1.9 now uses a thread pool with a configurable minimum and
 maximum number of threads.  Use the command line options
 <tt>--min-threads</tt> and <tt>--max-threads</tt> if the defaults
-don't suite your needs.  Run <tt>svnserve --help</tt> to your
-system's defaults and whether the options are available at all.
+don't suite your needs.
 </p>
   
 <div class="notice">
@@ -895,6 +894,12 @@ system's defaults and whether the option
   long-running reports like checkout or export, connections with waiting
   requests may eventually time out.</p>
 </div>
+
+<p>Whether or not the new options are available depends on the platform
+and APR capabilities.  Also, the default for <tt>--max-threads</tt> is
+lower on 32 bit systems than on 64 bit ones.  Run <tt>svnserve --help</tt>
+to see your system's defaults and whether the options are available at all.
+</p>
   
 </div> <!-- rate-limiting-svnserve -->
 
@@ -1178,9 +1183,15 @@ legitimate out-of-date condition and ret
 will fix the problem.
 </p>
 
-<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>This problem is not new to Subversion 1.9 and limited to repositories
+with high commit frequencies.  Triggering it requires either pre-1.7
+clients, a pre-1.7 server or a server that has HTTPv2 explicitly disabled
+via the <tt>SVNAdvertiseV2Protocol off</tt> option.  To avoid the problem,
+consider upgrading clients and configuring the server to use the HTTPv2
+protocol.
+</p>
+
+<p>svnserve and local repository access are not affected.
 </p>
 
 </div>  <!-- httpv1-commit-race -->



Mime
View raw message