[svnbook] r4366 committed - Merge from ^/trunk/en r4364 (don't say commit can't carry arbitrary re...

svnbook at googlecode.com svnbook at googlecode.com
Fri Jan 25 13:06:58 CST 2013


Revision: 4366
Author:   cmpilato at gmail.com
Date:     Fri Jan 25 11:06:49 2013
Log:      Merge from ^/trunk/en r4364 (don't say commit can't carry  
arbitrary revprops).
http://code.google.com/p/svnbook/source/detail?r=4366

Modified:
  /branches/1.6/en
  /branches/1.6/en/book/ch05-repository-admin.xml

=======================================
--- /branches/1.6/en/book/ch05-repository-admin.xml	Fri Sep  9 08:27:07 2011
+++ /branches/1.6/en/book/ch05-repository-admin.xml	Fri Jan 25 11:06:49 2013
@@ -2843,18 +2843,17 @@

        <para>Of particular interest here is that for each mirrored
          revision, there is first a commit of that revision to the
-        target repository, and then property changes follow.  This is
-        because the initial commit is performed by (and attributed to)
-        the user <literal>syncuser</literal>, and it is datestamped
-        with the time as of that revision's creation.  Also,
-        Subversion's underlying repository access interfaces don't
-        provide a mechanism for setting arbitrary revision properties
-        as part of a commit.  So <command>svnsync</command> follows up
-        with an immediate series of property modifications that copy
-        into the target repository all the revision properties found
-        for that revision in the source repository.  This also has the
-        effect of fixing the author and datestamp of the revision to
-        match that of the source repository.</para>
+        target repository, and then property changes follow.  This
+        two-phase replication is required because the initial commit
+        is performed by (and attributed to) the user
+        <literal>syncuser</literal> and is datestamped with the time
+        as of that revision's creation.  <command>svnsync</command>
+        has to follow up with an immediate series of property
+        modifications that copy into the target repository all the
+        original revision properties found for that revision in the
+        source repository, which also has the effect of fixing the
+        author and datestamp of the revision to match that of the
+        source repository.</para>

        <para>Also noteworthy is that <command>svnsync</command>
          performs careful bookkeeping that allows it to be safely




More information about the svnbook-dev mailing list