svn commit: r1929792 - subversion/site/publish

Author: dsahlberg
Date: Sun Nov 16 14:38:53 2025
New Revision: 1929792

Log:
In site/publish:

Merge 1929791 from site/staging

Fix some broken links

* news.html
  (#news-20220412-1.10.8): Add # to a section link.
  (#news-20110724): Release note links don't contain the patch version.

* faq.html
  (#sorry-no-globbing): tools_contrib.html was removed in r900549 (2010).
  (#multi-merge): Remove dead external link to svn-merge-repos.pl.
  (#dumpload): Github archeology indicate the Git repo was only ever a copy
    of the borg.ch original. Potential other source is
    https://github.com/imrivera/svndumptool

Modified:
   subversion/site/publish/   (props changed)
   subversion/site/publish/faq.html
   subversion/site/publish/news.html   (contents, props changed)

Modified: subversion/site/publish/faq.html
==============================================================================
--- subversion/site/publish/faq.html	Sun Nov 16 14:36:27 2025	(r1929791)
+++ subversion/site/publish/faq.html	Sun Nov 16 14:38:53 2025	(r1929792)
@@ -1259,8 +1259,6 @@ equivalent to CVS modules:</p>
 <p>There are also some helpful tools floating around on the internet,
 to select and reorder revisions when merging
 several repositories.  For instance the 
-<a href="https://www.cri.ensmp.fr/people/coelho/svn-merge-repos.html">svn-merge-repos.pl</a> 
-perl script for basic operations and the
 <a href="https://svn.borg.ch/svndumptool/">SvnDumpTool</a> python classes
 for advanced reorganisations.</p>
 </div>
@@ -1758,7 +1756,7 @@ history).  Again, you can ignore this wi
 But since this is a corruption "in history", this can only be repaired
 with a dump+load, so this might be a good time to try and fix this (or
 you'll run into this again in the future).  To repair it you can use
-a tool like <a href="https://github.com/jwiegley/svndumptool">svndumptool</a>.
+a tool like <a href="https://svn.borg.ch/svndumptool/">svndumptool</a>.
 But it only works on dump <i>files</i>, not as part of a pipe.  So a possible
 way to go about it is: dump that single
 (corrupt) revision to a file, repair it ('svndumptool.py eolfix-prop
@@ -2763,8 +2761,7 @@ generates just one commit total.
 <p>
 There is a program called "svnmucc" (previously "mucc"), whose source is
 distributed with Subversion, that enables you to combine multiple
-commands into one commit. See <a href="tools_contrib.html#svnmucc_c">the
-Tools and Contrib page</a>.
+commands into one commit. For more information, see <pre>$ svnmucc help</pre>
 </p>
 </div>
 

Modified: subversion/site/publish/news.html
==============================================================================
--- subversion/site/publish/news.html	Sun Nov 16 14:36:27 2025	(r1929791)
+++ subversion/site/publish/news.html	Sun Nov 16 14:38:53 2025	(r1929792)
@@ -157,7 +157,7 @@ on 2022-04-12 and is available to anyone
 
 <div class="h3" id="news-20220412-1.10.8"> 
 <h3>2022-04-12 &mdash; Apache Subversion 1.10.8 Released
-   <a class="sectionlink" href="news-20220412-1.10.8"
+   <a class="sectionlink" href="#news-20220412-1.10.8"
    title="Link to this section">&para;</a> 
 </h3> 
    
@@ -2116,7 +2116,7 @@ candidate will become the final release
  and maintainers.  Please see the
  <a href="https://svn.haxx.se/dev/archive-2011-07/0696.shtml">release
  announcement</a> for more information about this release, and the
- <a href="/docs/release-notes/1.7.0.html">release notes</a> and 
+ <a href="/docs/release-notes/1.7.html">release notes</a> and 
  <a href="https://svn.apache.org/repos/asf/subversion/tags/1.7.0-beta2/CHANGES"> 
  change log</a> for information about what will eventually be
  in the 1.7.0 release.</p>