[svnbook commit] r1457 - trunk/src/en/book

sussman svnbook-dev at red-bean.com
Thu Jun 16 13:08:06 CDT 2005


Author: sussman
Date: Thu Jun 16 13:08:04 2005
New Revision: 1457

Modified:
   trunk/src/en/book/ch07.xml
Log:
* src/en/book/ch07.xml:  whoops, fix the busted sidebar.

Modified: trunk/src/en/book/ch07.xml
==============================================================================
--- trunk/src/en/book/ch07.xml	(original)
+++ trunk/src/en/book/ch07.xml	Thu Jun 16 13:08:04 2005
@@ -2231,35 +2231,28 @@
           <para>Subversion defaults to the <quote>softer</quote>
             approach, but still allows administrators to create
             stricter enforcement policies through the use of hook
-            scripts.  (To learn more about hooks, see
-            <xref linkend="svn.reposadmin.create.hooks"/>.)</para>
-
-          <para>In particular, the <filename>pre-lock</filename>
+            scripts.  In particular, the <filename>pre-lock</filename>
             and <filename>pre-unlock</filename> hooks allow
             administrators to decide when lock creation and lock
-            releases are allowed to happen.  For example, an
-            administrator can disable the locking feature completely
-            by making <filename>pre-lock</filename> always return
-            failure.  Depending on whether or not a lock already
-            exists, a <filename>pre-lock</filename>
-            or <filename>pre-unlock</filename> hook program can decide
-            whether or not to allow a certain user to break or steal
-            the lock.  The <filename>post-lock</filename>
+            releases are allowed to happen.  Depending on whether or
+            not a lock already exists, these two hooks can decide
+            whether or not to allow a certain user to break or steal a
+            lock.  The <filename>post-lock</filename>
             and <filename>post-unlock</filename> hooks are also
-            available, and serve the same purpose
-            as <filename>post-commit</filename>: communication.
-            Administrators may want to send e-mails whenever somebody
-            locks or unlocks a file, to help remind users of exactly
-            how file access is being serialized.</para>
+            available, and can be used to send email after locking
+            actions.</para>
+
+          <para>To learn more about repository hooks, see
+            <xref linkend="svn.reposadmin.create.hooks"/>.</para>
         </sidebar>
 
     </sect2>
 
-
     <sect2 id="svn.advanced.locking.prevent-wasted-time">
       <title>Preventing wasted time</title>
 
       
+      
 
 
     </sect2>



More information about the svnbook-dev mailing list