svn commit: r1702432 - /subversion/site/publish/docs/release-notes/1.9.html

[ph...@apache.org]

Author: philip
Date: Fri Sep 11 11:38:25 2015
New Revision: 1702432

URL: http://svn.apache.org/r1702432
Log:
* docs/release-notes/1.9.html
  Add #locking-post-hooks.

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=1702432&r1=1702431&r2=1702432&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Fri Sep 11 11:38:25 2015
@@ -1352,7 +1352,7 @@ for GET requests.</p>
 </div> <!-- lock-http-pipelining -->
 
 <div class="h3" id="locking-multiple-files">
-<h3>Locking Multiple Files
+<h3>Locking multiple files
   <a class="sectionlink" href="#locking-multiple-files"
      title="Link to this section">&para;</a>
 </h3>
@@ -1366,7 +1366,7 @@ significant when the total number of loc
 
 <p>The default behaviour for commits is to automatically release locks
 after a successful commit and this takes advantage of the more
-efficient lock process.  In previous versions the disk IO involved in
+efficient lock process.  In previous releases the disk IO involved in
 releasing the locks would sometimes be greater than that involved in
 creating the new revision.</p>
 
@@ -1377,6 +1377,23 @@ the client still sends multiple LOCK and
 
 </div> <!-- locking-multiple-files -->
 
+<div class="h3" id="locking-post-hooks">
+<h3>Multiple paths in post-lock and post-unlock hooks
+  <a class="sectionlink" href="#locking-post-hooks"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>The post-lock and post-unlock hooks receive multiple paths via
+standard input.  In previous releases the repository backends always
+operated on a single path at a time so only one path was ever passed
+to the hook.  In 1.9 when multiple paths are locked or unlocked in a
+single operation multiple paths will be passed to the hook.</p>
+
+<p>The pre-lock and pre-unlock hooks continue to be passed a single
+path as a parameter.</p>
+
+</div> <!-- locking-post-hooks -->
+
 </div>  <!-- enhancements -->
 
 <div class="h2" id="issues">