[svnbook commit] r1443 - in trunk/src/en: . book

cmpilato svnbook-dev at red-bean.com
Tue Jun 14 23:39:42 CDT 2005

Author: cmpilato
Date: Tue Jun 14 23:39:41 2005
New Revision: 1443

Document the --use-pre-commit-hook and --use-post-commit-hook
options to 'svnadmin load'.

* src/en/TODO
  Finish a TODO.

* src/en/book/ch05.xml
  (Migrating a Repository):  Document the use of the options.

* src/en/book/ch09.xml
  (svnadmin): Describe the options.

Modified: trunk/src/en/TODO
--- trunk/src/en/TODO	(original)
+++ trunk/src/en/TODO	Tue Jun 14 23:39:41 2005
@@ -16,9 +16,6 @@
       - Added fifth ACTION argument (A, M, or D)
       - New/old revprop value available on stdin
-  * ch05: document the --use-[pre|post]-commit-hook option to
-    'svnadmin load'.  [MIKE]
   * ch06: client-cred-caching: mention win32 encryption in
     mod_authz_svn: groups can contain other groups [BEN]

Modified: trunk/src/en/book/ch05.xml
--- trunk/src/en/book/ch05.xml	(original)
+++ trunk/src/en/book/ch05.xml	Tue Jun 14 23:39:41 2005
@@ -2278,6 +2278,25 @@
+      <para>The result of a load is new revisions added to a
+        repository—the same thing you get by making commits
+        against that repository from a regular Subversion client.  And
+        just as in a commit, you can use hook scripts to perform
+        actions before and after each of the commits made during a load
+        process.  By passing the <option>--use-pre-commit-hook</option> 
+        and <option>--use-post-commit-hook</option> options to
+        <command>svnadmin load</command>, you can instruct Subversion
+        to execute the pre-commit and post-commit hook scripts,
+        respectively, for each loaded revision.  You might use these,
+        for example, to ensure that loaded revisions pass through the
+        same validation steps that regular commits pass through.  Of
+        course, you should use these options with care—if your
+        post-commit hook sends emails to a mailing list for each new
+        commit, you might not want to spew hundreds or thousands of
+        commit emails in rapid succession at that list for each of the
+        loaded revisions!  You can read more about the use of hook 
+        scripts in <xref linkend="svn.reposadmin.create.hooks"/>.</para>
       <para>Note that because <command>svnadmin</command> uses
         standard input and output streams for the repository dump and
         load process, people who are feeling especially saucy can try
@@ -2431,7 +2450,7 @@
         it should be relatively easy to describe generic sets of
         changes—each of which should be treated as a new
         revision—using this file format.  In fact, the
-        <command>cvs2svn.py</command> utility (see <xref
+        <command>cvs2svn</command> utility (see <xref
         linkend="svn.forcvs.convert"/>) uses the dump format to represent the
         contents of a CVS repository so that those contents can be
         moved in a Subversion repository.</para>

Modified: trunk/src/en/book/ch09.xml
--- trunk/src/en/book/ch09.xml	(original)
+++ trunk/src/en/book/ch09.xml	Tue Jun 14 23:39:41 2005
@@ -3917,6 +3917,26 @@
+        <varlistentry>
+          <term><option>--use-post-commit-hook</option></term>
+          <listitem>
+            <para>When loading a dump file, run the repository's
+              post-commit hook after finalizing each newly loaded
+              revision.</para>
+          </listitem>
+        </varlistentry>
+        <varlistentry>
+          <term><option>--use-pre-commit-hook</option></term>
+          <listitem>
+            <para>When loading a dump file, run the repository's
+              pre-commit hook before finalizing each newly loaded
+              revision.  If the hook fails, abort the commit and
+              terminate the load process.</para>
+          </listitem>
+        </varlistentry>

More information about the svnbook-dev mailing list