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

cmpilato noreply at red-bean.com
Wed Jun 11 21:10:07 CDT 2008


Author: cmpilato
Date: Wed Jun 11 21:10:06 2008
New Revision: 3121

Log:
* src/en/book/ch05-repository-admin.xml
  Fixes based on review by Daniel Shahaf <d.s at daniel.shahaf.co.il>.


Modified:
   trunk/src/en/book/ch05-repository-admin.xml

Modified: trunk/src/en/book/ch05-repository-admin.xml
==============================================================================
--- trunk/src/en/book/ch05-repository-admin.xml	(original)
+++ trunk/src/en/book/ch05-repository-admin.xml	Wed Jun 11 21:10:06 2008
@@ -3124,19 +3124,19 @@
 </screen>
 
       <para>For folks using versions of Subversion earlier than 1.5,
-        these tasks are a little more complicated.  You can set an
-        explicit UUID on a repository by creating a stub repository
-        dump file that carries that UUID specification, and then
-        loading that into your repository with the
-        <option>--force-uuid</option> option to <command>svnadmin
-        load</command>.</para>
+        these tasks are a little more complicated.  You can explicitly
+        set a repository's UUID by piping a repository dump file stub
+        that carries the new UUID specification through
+        <command>svnadmin load --force-uuid</command>.</para>
 
       <screen>
-$ cat - <<EOF | svnadmin load --force-uuid /var/svn/repos
+$ svnadmin load --force-uuid /var/svn/repos <<EOF
 SVN-fs-dump-format-version: 2
 
 UUID: cf2b9d22-acb5-11dc-bc8c-05e83ce5dbec
 EOF
+$ svnlook uuid /var/svn/repos
+cf2b9d22-acb5-11dc-bc8c-05e83ce5dbec
 $
 </screen>
 
@@ -3174,7 +3174,7 @@
       configuration bits for a now-deleted repository.  If you have
       automated processes that publish information from or about your
       repositories, they may need to be updated.  Hook scripts might
-      need to be reconfigured.  Users need to be notified.  The list
+      need to be reconfigured.  Users may need to be notified.  The list
       can go on indefinitely, or at least to the extent that you've
       built processes and procedures around your Subversion
       repository.</para>




More information about the svnbook-dev mailing list