[svnbook] r3968 committed - Update some web/email references.

svnbook at googlecode.com svnbook at googlecode.com
Tue Aug 9 10:00:11 CDT 2011


Revision: 3968
Author:   cmpilato at gmail.com
Date:     Tue Aug  9 07:57:26 2011
Log:      Update some web/email references.
http://code.google.com/p/svnbook/source/detail?r=3968

Modified:
  /trunk/src/en/book/ch05-repository-admin.xml
  /trunk/src/en/book/ch08-embedding-svn.xml
  /trunk/src/en/book/foreword.xml

=======================================
--- /trunk/src/en/book/ch05-repository-admin.xml	Fri Jul 29 10:45:04 2011
+++ /trunk/src/en/book/ch05-repository-admin.xml	Tue Aug  9 07:57:26 2011
@@ -1923,7 +1923,7 @@
          (perhaps by renaming it to something like
          <filename>repos.BROKEN</filename>) and then restore your
          latest backup of it.  Then, send an email to the Subversion
-        users mailing list (at <email>users at subversion.tigris.org</email>)
+        users mailing list (at <email>users at subversion.apache.org</email>)
          describing your problem in detail.  Data integrity is an
          extremely high priority to the Subversion developers.</para>

=======================================
--- /trunk/src/en/book/ch08-embedding-svn.xml	Tue Aug  2 13:06:37 2011
+++ /trunk/src/en/book/ch08-embedding-svn.xml	Tue Aug  9 07:57:26 2011
@@ -750,12 +750,13 @@
      <para>Another good source of information about programming against
        the Subversion APIs is the project's own hacking guidelines,
        which you can find at
-      <ulink url="http://subversion.tigris.org/hacking.html" />.  This
-      document contains useful information, which, while aimed at
-      developers and would-be developers of Subversion itself, is
-      equally applicable to folks developing against Subversion as a
-      set of third-party libraries.<footnote><para>After all,
-      Subversion uses Subversion's APIs, too.</para></footnote></para>
+      <ulink url="http://subversion.apache.org/docs/community-guide/"
+      />.  This document contains useful information, which, while
+      aimed at developers and would-be developers of Subversion
+      itself, is equally applicable to folks developing against
+      Subversion as a set of third-party
+      libraries.<footnote><para>After all, Subversion uses
+      Subversion's APIs, too.</para></footnote></para>

      <!-- ===============================================================  
-->
      <sect2 id="svn.developer.usingapi.apr">
@@ -927,10 +928,7 @@
        <para>It's worth noting here that there are other options for
          interfacing with Subversion using other languages:  alternative
          bindings for Subversion that aren't provided by the
-        Subversion development community at all.  You can find links
-        to these alternative bindings on the Subversion project's
-        links page (at <ulink
-        url="http://subversion.tigris.org/links.html" />), but there
+        Subversion development community at all.  There
          are a couple of popular ones we feel are especially
          noteworthy.  First, Barry Scott's PySVN bindings (<ulink
          url="http://pysvn.tigris.org/" />) are a popular option for
=======================================
--- /trunk/src/en/book/foreword.xml	Sat Aug  2 08:38:01 2008
+++ /trunk/src/en/book/foreword.xml	Tue Aug  9 07:57:26 2011
@@ -108,7 +108,7 @@
      eerily telepathic; yet occasionally, you will stumble into a
      hole in the community's knowledge and come away empty-handed.
      When this happens, the best thing you can do is email
-    <email>users at subversion.tigris.org</email> and present your
+    <email>users at subversion.apache.org</email> and present your
      problem.  The authors are still there and still watching, and the
      authors include not just the three listed on the cover, but many others
      who contributed corrections and original material.  From the




More information about the svnbook-dev mailing list