[svnbook] r4364 committed - Finish issue 141 ("ch05: Revisit the truth of a statement about...

svnbook at googlecode.com svnbook at googlecode.com
Fri Jan 25 13:03:56 CST 2013


Revision: 4364
Author:   cmpilato at gmail.com
Date:     Fri Jan 25 11:03:44 2013
Log:      Finish issue 141 ("ch05: Revisit the truth of a statement about
commits of custom properties").

* en/book/ch05-repository-admin.xml
   (svn.reposadmin.maint.replication.svnsync): Tweak a paragraph to not
     claim that Subversion can't propogate arbitrary revprops during
     commit time.  It actually can.
http://code.google.com/p/svnbook/source/detail?r=4364

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

=======================================
--- /trunk/en/book/ch05-repository-admin.xml	Tue Nov  8 08:54:48 2011
+++ /trunk/en/book/ch05-repository-admin.xml	Fri Jan 25 11:03:44 2013
@@ -2973,18 +2973,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