subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmpil...@apache.org
Subject svn commit: r1490643 - /subversion/site/publish/docs/release-notes/1.8.html
Date Fri, 07 Jun 2013 13:39:31 GMT
Author: cmpilato
Date: Fri Jun  7 13:39:31 2013
New Revision: 1490643

URL: http://svn.apache.org/r1490643
Log:
* sites/publish/docs/release-notes/1.8.html
  (#svnmasterversion): Clarify that the SVNMasterVersion directive can
    only inform regarding the *default* feature support in the master
    server.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1490643&r1=1490642&r2=1490643&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Fri Jun  7 13:39:31 2013
@@ -2209,6 +2209,18 @@ SVNMasterVersion 1.7.7
 </Location>
 </pre>
 
+<div class="notice">
+<p>In the general case, the new <tt>SVNMasterVersion</tt> directive
+supercedes the need for <tt>SVNAdvertiseV2Protocol</tt>.  By declaring
+the version of the master server, the slave will assume the default
+level of feature support for that server.  However, if you have a
+master server which <em>can</em> support the HTTPv2 protocol but for
+which you've disabled this intentionally, you will need to also
+explicitly disable the feature (again, via
+the <tt>SVNAdvertiseV2Protocol off</tt> directive) in your slave
+servers as well.</p>
+</div>
+
 </div>  <!-- svnmasterversion -->
 
 <div class="h3" id="davkeywordexpansion">



Mime
View raw message