[svnbook] r6040 committed - trunk/en/book

[danielsahlberg at users.sourceforge.net]

Revision: 6040
          http://sourceforge.net/p/svnbook/source/6040
Author:   danielsahlberg
Date:     2021-08-25 18:43:21 +0000 (Wed, 25 Aug 2021)
Log Message:
-----------
Replace a few tigris.org links.

* en/book/appb-svn-for-cvs-users.xml: cvs2svn is at github.

* en/book/ch06-server-configuration.xml: The issuetracker is in JIRA (but link
  through the subversion.apache.org/issueXXXX redirect in case JIRA is moved
  in the future).

Modified Paths:
--------------
    trunk/en/book/appb-svn-for-cvs-users.xml
    trunk/en/book/ch06-server-configuration.xml

Modified: trunk/en/book/appb-svn-for-cvs-users.xml
===================================================================
--- trunk/en/book/appb-svn-for-cvs-users.xml	2021-08-16 20:57:39 UTC (rev 6039)
+++ trunk/en/book/appb-svn-for-cvs-users.xml	2021-08-25 18:43:21 UTC (rev 6040)
@@ -523,7 +523,7 @@
       existing CVS repositories into Subversion ones.</para>
 
     <para>The most popular (and mature) conversion tool is
-      cvs2svn (<ulink url="http://cvs2svn.tigris.org/"/>), a Python
+      cvs2svn (<ulink url="https://github.com/mhagger/cvs2svn/"/>), a Python
       program originally created by members of Subversion's own
       development community.  This tool is meant to run exactly once:
       it scans your CVS repository multiple times and attempts to

Modified: trunk/en/book/ch06-server-configuration.xml
===================================================================
--- trunk/en/book/ch06-server-configuration.xml	2021-08-16 20:57:39 UTC (rev 6039)
+++ trunk/en/book/ch06-server-configuration.xml	2021-08-25 18:43:21 UTC (rev 6040)
@@ -3914,7 +3914,7 @@
             of the mechanisms that one might employ to accomplish this
             replication fall short in one way or
             another<footnote><para><ulink
-            url="http://subversion.tigris.org/issues/show_bug.cgi?id=3457"
+            url="https://subversion.apache.org/issue3457"
             /> tracks these problems.</para></footnote>.  Many teams
             don't use Subversion's locking features at all, so this
             may be a nonissue for you.  Sadly, for those teams which