[svnbook] r4177 committed - * en/book/ch02-basic-usage.xml,...

svnbook at googlecode.com svnbook at googlecode.com
Tue Nov 8 10:55:09 CST 2011


Revision: 4177
Author:   cmpilato at gmail.com
Date:     Tue Nov  8 08:54:48 2011
Log:      * en/book/ch02-basic-usage.xml,
* en/book/ch03-advanced-topics.xml,
* en/book/ch04-branching-and-merging.xml,
* en/book/ch05-repository-admin.xml,
* en/book/ch06-server-configuration.xml
   Try another approach to fixing links to Reference sections, adding
   the text 'in <xref linkend="svn.ref"/>' after each such reference in
   the book that points to an ambiguously named piece of the Reference.

http://code.google.com/p/svnbook/source/detail?r=4177

Modified:
  /trunk/en/book/ch02-basic-usage.xml
  /trunk/en/book/ch03-advanced-topics.xml
  /trunk/en/book/ch04-branching-and-merging.xml
  /trunk/en/book/ch05-repository-admin.xml
  /trunk/en/book/ch06-server-configuration.xml

=======================================
--- /trunk/en/book/ch02-basic-usage.xml	Sat Nov  5 16:04:49 2011
+++ /trunk/en/book/ch02-basic-usage.xml	Tue Nov  8 08:54:48 2011
@@ -582,7 +582,8 @@
          to each item to let you know what actions Subversion performed
          to bring your working copy up to date.  To find out what these
          letters mean, run <userinput>svn help update</userinput> or
-        see <xref linkend="svn.ref.svn.c.update"/>.</para>
+        see <xref linkend="svn.ref.svn.c.update"/> in
+        <xref linkend="svn.ref"/>.</para>

      </sect2>

@@ -1022,7 +1023,8 @@
            copy than we've shown here—for an exhaustive
            description of <command>svn status</command> and its output,
            run <userinput>svn help status</userinput> or see
-          <xref linkend="svn.ref.svn.c.status"/>.</para>
+          <xref linkend="svn.ref.svn.c.status"/> in
+          <xref linkend="svn.ref"/>.</para>

        </sect3>

=======================================
--- /trunk/en/book/ch03-advanced-topics.xml	Sun Nov  6 14:38:12 2011
+++ /trunk/en/book/ch03-advanced-topics.xml	Tue Nov  8 08:54:48 2011
@@ -736,7 +736,8 @@
        these properties are mentioned elsewhere in this or other
        chapters as part of the more general topics to which they are
        related.  For an exhaustive list of Subversion's predefined
-      properties, see <xref linkend="svn.ref.properties" />.</para>
+      properties, see <xref linkend="svn.ref.properties" /> in
+      <xref linkend="svn.ref"/>.</para>

      <note>
        <para>While Subversion automatically attaches properties
@@ -1282,7 +1283,8 @@
          1.7 or better can be automatically applied to a working copy
          by the <command>svn patch</command> command.  For more
          about <command>svn patch</command>, see
-        <xref linkend="svn.ref.svn.c.patch" />.</para>
+        <xref linkend="svn.ref.svn.c.patch" /> in
+        <xref linkend="svn.ref"/>.</para>

        <note>
          <para>There's one exception to how property changes are
@@ -2295,7 +2297,8 @@
          can use this program, plus some additional tooling, to embed
          that revision information into your files.  For more
          information on <command>svnversion</command>, see <xref
-        linkend="svn.ref.svnversion"/>.</para>
+        linkend="svn.ref.svnversion"/> in
+        <xref linkend="svn.ref"/>.</para>

      </sidebar>

@@ -4420,9 +4423,10 @@
          author of the revision.  That is, the authenticated user's
          name is stored as the value of the
          <literal>svn:author</literal> property on the new revision
-        (see <xref linkend="svn.ref.properties"/>).  If
-        the client was not authenticated (i.e., if the server
-        never issued an authentication challenge), the revision's
+        (see <xref linkend="svn.ref.properties"/> in
+        <xref linkend="svn.ref"/>).  If the client was not
+        authenticated (i.e., if the server never issued an
+        authentication challenge), the revision's
          <literal>svn:author</literal> property is empty.</para>

      </sect2>
=======================================
--- /trunk/en/book/ch04-branching-and-merging.xml	Tue Nov  8 08:45:46 2011
+++ /trunk/en/book/ch04-branching-and-merging.xml	Tue Nov  8 08:54:48 2011
@@ -2936,8 +2936,9 @@
        future.<footnote><para>You <emphasis>can</emphasis>, however,
        use <command>svn relocate</command> if the URL of your server
        changes and you don't want to abandon an existing working copy.
-      See <xref linkend="svn.ref.svn.c.relocate"/> for more information
-      and an example.</para></footnote></para>
+      See <xref linkend="svn.ref.svn.c.relocate"/> in
+      <xref linkend="svn.ref"/> for more information and an
+      example.</para></footnote></para>

      <tip>
        <para>Administrators who need to change the URL of a repository
=======================================
--- /trunk/en/book/ch05-repository-admin.xml	Thu Nov  3 12:11:16 2011
+++ /trunk/en/book/ch05-repository-admin.xml	Tue Nov  8 08:54:48 2011
@@ -123,8 +123,8 @@
          a <filename>dav</filename> subdirectory
          unless <filename>mod_dav_svn</filename> is in use and hasn't
          been configured to store its activities database elsewhere.
-        See <xref linkend="svn.ref.mod_dav_svn.conf.directives"/> for
-        more information.</para>
+        See <xref linkend="svn.ref.mod_dav_svn.conf.directives"/> in
+        <xref linkend="svn.ref"/> for more information.</para>
      </note>

      <para>Of course, when accessed via the Subversion libraries, this
@@ -963,7 +963,8 @@

        <para>There are several hooks implemented by the Subversion
          repository, and you can get details about each of them in
-        <xref linkend="svn.ref.reposhooks" />.  As a repository
+        <xref linkend="svn.ref.reposhooks" /> in
+        <xref linkend="svn.ref"/>.  As a repository
          administrator, you'll need to decide which hooks you wish
          to implement (by way of providing an appropriately named and
          permissioned hook program), and how.  When you make this
@@ -1119,8 +1120,9 @@
            introduced to the <command>svnadmin create</command>
            subcommand.  Most of the other <command>svnadmin</command>
            subcommands we will cover later in this chapter.  And you
-          can consult <xref linkend="svn.ref.svnadmin" /> for a full
-          rundown of subcommands and what each of them offers.</para>
+          can consult <xref linkend="svn.ref.svnadmin" /> in
+          <xref linkend="svn.ref"/> for a full rundown of subcommands
+          and what each of them offers.</para>

        </sect3>

@@ -1258,7 +1260,8 @@
            directory trees, reporting which paths were modified in a
            given revision or transaction, showing textual and property
            differences made to files and directories, and so on.  See
-          <xref linkend="svn.ref.svnlook" /> for a full reference of
+          <xref linkend="svn.ref.svnlook" /> in
+          <xref linkend="svn.ref"/> for a full reference of
            <command>svnlook</command>'s features.</para>

        </sect3>
@@ -1477,7 +1480,8 @@
          this log message after the commit is finished, the user
          can <quote>fix</quote> her log message remotely using
          <command>svn propset</command> (see <xref
-        linkend="svn.ref.svn.c.propset"/>).  However, because of the
+        linkend="svn.ref.svn.c.propset"/> in
+        <xref linkend="svn.ref"/>).  However, because of the
          potential to lose information forever, Subversion repositories
          are not, by default, configured to allow changes to
          unversioned properties—except by an
@@ -1820,8 +1824,9 @@

          <para>Subversion can pack existing sharded repositories which
            have been upgraded to the 1.6 filesystem format or later (see
-          <xref linkend="svn.ref.svnadmin.c.upgrade"/>).  To do so,
-          just run <command>svnadmin pack</command> on the
+          <xref linkend="svn.ref.svnadmin.c.upgrade"/>) in
+          <xref linkend="svn.ref"/>.  To do so, just
+          run <command>svnadmin pack</command> on the
            repository:</para>

          <informalexample>
@@ -2341,8 +2346,8 @@
              committing new revisions, <command>svnrdump load</command>
              requires that the target repository have revision property
              changes enabled via the pre-revprop-change hook.  See
-            <xref linkend="svn.ref.reposhooks.pre-revprop-change" />
-            for details.</para>
+            <xref linkend="svn.ref.reposhooks.pre-revprop-change" /> in
+            <xref linkend="svn.ref"/> for details.</para>
          </note>

          <para>As you might expect, you can use
@@ -2741,12 +2746,13 @@
            within the framework of that repository's hook system, the
            default state of the repository (which is to disallow revision
            property changes; see <xref
-          linkend="svn.ref.reposhooks.pre-revprop-change" />) is
-          insufficient.  You'll need to explicitly implement the
-          pre-revprop-change hook, and your script must allow
-          <command>svnsync</command> to set and change revision
-          properties.  With those provisions in place, you are ready to
-          start mirroring repository revisions.</para>
+          linkend="svn.ref.reposhooks.pre-revprop-change" /> in
+          <xref linkend="svn.ref"/>) is insufficient.  You'll need to
+          explicitly implement the pre-revprop-change hook, and your
+          script must allow <command>svnsync</command> to set and
+          change revision properties.  With those provisions in place,
+          you are ready to start mirroring repository
+          revisions.</para>

          <tip>
            <para>It's a good idea to implement authorization measures
@@ -3287,19 +3293,19 @@
            <command>svn relocate</command> to point your working
            copy to whichever of the repositories you wish to operate
            against, a process that is described in
-          <xref linkend="svn.ref.svn.c.relocate" />.  There is a
-          possible danger here, though, in that if the primary and
-          mirror repositories aren't in close synchronization, a
-          working copy up to date with, and pointing to, the primary
-          repository will, if relocated to point to an out-of-date
-          mirror, become confused about the apparent sudden loss of
-          revisions it fully expects to be present, and it will throw
-          errors to that effect.  If this occurs, you can relocate
-          your working copy back to the primary repository and then
-          either wait until the mirror repository is up to date, or
-          backdate your working copy to a revision you know is present
-          in the sync repository, and then retry the
-          relocation.</para>
+          <xref linkend="svn.ref.svn.c.relocate" /> in
+          <xref linkend="svn.ref"/>.  There is a possible danger here,
+          though, in that if the primary and mirror repositories
+          aren't in close synchronization, a working copy up to date
+          with, and pointing to, the primary repository will, if
+          relocated to point to an out-of-date mirror, become confused
+          about the apparent sudden loss of revisions it fully expects
+          to be present, and it will throw errors to that effect.  If
+          this occurs, you can relocate your working copy back to the
+          primary repository and then either wait until the mirror
+          repository is up to date, or backdate your working copy to a
+          revision you know is present in the sync repository, and
+          then retry the relocation.</para>

          <para>Finally, be aware that the revision-based replication
            provided by <command>svnsync</command> is only
=======================================
--- /trunk/en/book/ch06-server-configuration.xml	Thu Nov  3 12:47:55 2011
+++ /trunk/en/book/ch06-server-configuration.xml	Tue Nov  8 08:54:48 2011
@@ -3271,8 +3271,8 @@
            to mention in this chapter.  For a complete list of
            all <filename>httpd.conf</filename> directives
            that <command>mod_dav_svn</command> responds to, see
-          <xref linkend="svn.ref.mod_dav_svn.conf.directives"/>.</para>
-
+          <xref linkend="svn.ref.mod_dav_svn.conf.directives"/> in
+          <xref linkend="svn.ref"/>.</para>
        </sect3>
      </sect2>
    </sect1>




More information about the svnbook-dev mailing list