Author: danielsh
Date: Tue Apr 10 05:51:44 2012
New Revision: 1311580
URL: http://svn.apache.org/viewvc?rev=1311580&view=rev
Log:
* docs/release-notes/1.8.html
(hooks-post-commit): Add a concrete use-case.
(There should be one or two others on users@ archives.)
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=1311580&r1=1311579&r2=1311580&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Apr 10 05:51:44 2012
@@ -478,10 +478,14 @@ hook; it is the same as the second posit
<tt>pre-commit</tt>, and thus enables the <tt>pre-commit</tt> and
<tt>post-commit</tt> hooks to easily transfer state between them.</p>
-<p>For example, if the <tt>pre-commit</tt> hook makes an expensive computation
+<p>Generically, if the <tt>pre-commit</tt> hook makes an expensive computation
against the would-be-revision, it can store the result of that computation in a
persistent hash keyed by the transaction name, which the <tt>post-commit</tt>
-hook will use to avoid re-doing the computation.</p>
+hook will use to avoid re-doing the computation. One concrete usage of this
+would be to implement a pre-commit hook that tests compilability only, while
+a post-commit hook or a continuous integration tool runs more thorough tests
+--- on the binaries built at pre-commit, without having to rebuild them
+itself.</p>
</div> <!-- hooks-post-commit -->
