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

[cmpilato]

Author: cmpilato
Date: Wed May 28 22:16:16 2008
New Revision: 3089

Log:
* src/en/book/ch05-repository-admin.xml
  Add a blurb about partial mirrors.  (Trac ticket #101.)


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 May 28 22:16:16 2008
@@ -2821,6 +2821,28 @@
         that it is permitted to see.  Obviously such a mirror is not
         useful as a backup solution.</para>
 
+      <para>In Subversion 1.5, <command>svnsync</command> grew the
+        ability to also mirror a subset of a repository rather than
+        the whole thing.  The process of setting up and maintaining
+        such a mirror is exactly the same as when mirroring a whole
+        repository, except that instead of specifying the source
+        repository's root URL when running <command>svnsync
+        init</command>, you specify the URL of some subdirectory
+        within that repository.  Synchronization to that mirror will
+        now only copy the bits that changed under that source
+        repository subdirectory.  There are some limitations to this
+        support though.  First, you can't mirror multiple disjoint
+        subdirectories of the source repository into a single mirror
+        repository—you'd need to instead mirror some parent
+        directory that is common to both.  Secondly, the filtering
+        logic is entirely path-based, so if the subdirectory you are
+        mirroring was renamed at some point in the past, your mirror
+        would only contain the revisions since the directory appeared
+        at the URL you specified.  And likewise, if the source
+        subdirectory is renamed in the future, your synchronization
+        processes will stop mirroring data at the point that the
+        source URL you specified is no longer valid.</para>
+
       <para>As far as user interaction with repositories and mirrors
         goes, it <emphasis>is</emphasis> possible to have a single
         working copy that interacts with both, but you'll have to jump