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

svnbook at googlecode.com svnbook at googlecode.com
Wed Feb 6 10:08:45 CST 2013


Revision: 4399
Author:   cmpilato at gmail.com
Date:     Wed Feb  6 08:08:33 2013
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
   Update some links to reference material to be more precise.

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

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	Thu Jan 31 13:07:27 2013
+++ /trunk/en/book/ch02-basic-usage.xml	Wed Feb  6 08:08:33 2013
@@ -17,7 +17,7 @@
      encounter.  This chapter assumes that you've read and understood
      <xref linkend="svn.basic"/> and are familiar with the general
      model of Subversion.  For a complete reference of all commands,
-    see <xref linkend="svn.ref"/>.</para>
+    see <xref linkend="svn.ref.svn"/>.</para>

    <para>Also, this chapter assumes that the reader is seeking
      information about how to interact in a basic fashion with an
@@ -600,7 +600,7 @@
          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"/> in
-        <xref linkend="svn.ref"/>.</para>
+        <xref linkend="svn.ref.svn"/>.</para>

      </sect2>

@@ -1041,7 +1041,7 @@
            description of <command>svn status</command> and its output,
            run <userinput>svn help status</userinput> or see
            <xref linkend="svn.ref.svn.c.status"/> in
-          <xref linkend="svn.ref"/>.</para>
+          <xref linkend="svn.ref.svn"/>.</para>

        </sect3>

@@ -3291,7 +3291,7 @@
          Notable exceptions are those dealing with branching and
          merging (see <xref linkend="svn.branchmerge"/>) and properties (see
          <xref linkend="svn.advanced.props"/>).  However, you may want to
-        take a moment to skim through <xref linkend="svn.ref"/> to
+        take a moment to skim through <xref linkend="svn.ref.svn"/> to
          get an idea of all the different commands that Subversion
          has—and how you can use them to make your work
          easier.</para>
=======================================
--- /trunk/en/book/ch03-advanced-topics.xml	Thu Jan 31 13:21:47 2013
+++ /trunk/en/book/ch03-advanced-topics.xml	Wed Feb  6 08:08:33 2013
@@ -736,8 +736,7 @@
        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" /> in
-      <xref linkend="svn.ref"/>.</para>
+      properties, see <xref linkend="svn.ref.properties" />.</para>

      <note>
        <para>While Subversion automatically attaches properties
@@ -1284,7 +1283,7 @@
          by the <command>svn patch</command> command.  For more
          about <command>svn patch</command>, see
          <xref linkend="svn.ref.svn.c.patch" /> in
-        <xref linkend="svn.ref"/>.</para>
+        <xref linkend="svn.ref.svn"/>.</para>

        <note>
          <para>There's one exception to how property changes are
@@ -2827,8 +2826,7 @@
          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"/> in
-        <xref linkend="svn.ref"/>.</para>
+        linkend="svn.ref.svnversion"/>.</para>

      </sidebar>

@@ -4952,9 +4950,8 @@
          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"/> in
-        <xref linkend="svn.ref"/>).  If the client was not
-        authenticated (i.e., if the server never issued an
+        (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
          <literal>svn:author</literal> property is empty.</para>

=======================================
--- /trunk/en/book/ch04-branching-and-merging.xml	Tue Feb  5 08:18:19 2013
+++ /trunk/en/book/ch04-branching-and-merging.xml	Wed Feb  6 08:08:33 2013
@@ -1882,7 +1882,7 @@
        <para>A word of warning: while <command>svn diff</command> and
          <command>svn merge</command> are very similar in concept, they
          do have different syntax in many cases.  Be sure to read about
-        them in <xref linkend="svn.ref"/> for details, or ask
+        them in <xref linkend="svn.ref.svn"/> for details, or ask
          <command>svn help</command>.  For example, <command>svn
          merge</command> requires a working copy path as a target, that is,
          a place where it should apply the generated patch.  If the
@@ -3069,7 +3069,7 @@
        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"/> in
-      <xref linkend="svn.ref"/> for more information and an
+      <xref linkend="svn.ref.svn"/> for more information and an
        example.</para></footnote></para>

      <tip>
@@ -3265,8 +3265,8 @@
          work here.  In this case, you want to make a snapshot of your
          exact working copy arrangement and store it in the repository.
          Luckily, <command>svn copy</command> actually has four
-        different uses (which you can read about in <xref
-        linkend="svn.ref"/>), including the ability to copy a
+        different uses (see <xref linkend="svn.ref.svn.c.copy"/> in <xref
+        linkend="svn.ref.svn"/>), including the ability to copy a
          working copy tree to the repository:</para>

        <informalexample>
=======================================
--- /trunk/en/book/ch05-repository-admin.xml	Fri Feb  1 08:23:58 2013
+++ /trunk/en/book/ch05-repository-admin.xml	Wed Feb  6 08:08:33 2013
@@ -136,7 +136,9 @@
          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"/> in
-        <xref linkend="svn.ref"/> for more information.</para>
+        <xref linkend="svn.ref.mod_dav_svn.conf"/> for more
+        information.</para>
+
      </note>

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

        <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" /> in
-        <xref linkend="svn.ref"/>.  As a repository
+        <xref linkend="svn.ref.reposhooks" />.  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
@@ -1132,9 +1133,8 @@
            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" /> in
-          <xref linkend="svn.ref"/> for a full rundown of subcommands
-          and what each of them offers.</para>
+          can consult <xref linkend="svn.ref.svnadmin" /> for a full
+          rundown of subcommands and what each of them offers.</para>

        </sect3>

@@ -1272,8 +1272,7 @@
            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" /> in
-          <xref linkend="svn.ref"/> for a full reference of
+          <xref linkend="svn.ref.svnlook" /> for a full reference of
            <command>svnlook</command>'s features.</para>

        </sect3>
@@ -1493,7 +1492,7 @@
          can <quote>fix</quote> her log message remotely using
          <command>svn propset</command> (see <xref
          linkend="svn.ref.svn.c.propset"/> in
-        <xref linkend="svn.ref"/>).  However, because of the
+        <xref linkend="svn.ref.properties"/>).  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
@@ -1837,7 +1836,7 @@
          <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"/>) in
-          <xref linkend="svn.ref"/>.  To do so, just
+          <xref linkend="svn.ref.svnadmin"/>.  To do so, just
            run <command>svnadmin pack</command> on the
            repository:</para>

@@ -2359,7 +2358,7 @@
              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" /> in
-            <xref linkend="svn.ref"/> for details.</para>
+            <xref linkend="svn.ref.reposhooks"/> for details.</para>
          </note>

          <para>As you might expect, you can use
@@ -2759,12 +2758,12 @@
            default state of the repository (which is to disallow revision
            property changes; see <xref
            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>
+          <xref linkend="svn.ref.reposhooks"/>) 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
@@ -3305,7 +3304,7 @@
            copy to whichever of the repositories you wish to operate
            against, a process that is described in
            <xref linkend="svn.ref.svn.c.relocate" /> in
-          <xref linkend="svn.ref"/>.  There is a possible danger here,
+          <xref linkend="svn.ref.svn"/>.  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
=======================================
--- /trunk/en/book/ch06-server-configuration.xml	Tue Feb  5 10:17:09 2013
+++ /trunk/en/book/ch06-server-configuration.xml	Wed Feb  6 08:08:33 2013
@@ -3576,7 +3576,7 @@
            all <filename>httpd.conf</filename> directives
            that <command>mod_dav_svn</command> responds to, see
            <xref linkend="svn.ref.mod_dav_svn.conf.directives"/> in
-          <xref linkend="svn.ref"/>.</para>
+          <xref linkend="svn.ref.mod_dav_svn.conf"/>.</para>
        </sect3>
      </sect2>
    </sect1>




More information about the svnbook-dev mailing list