Author: dsahlberg
Date: Thu Jul 6 19:59:51 2023
New Revision: 1910824
URL: http://svn.apache.org/viewvc?rev=1910824&view=rev
Log:
In site/staging:
Remove or update outdated links
* faq.html
#ssh-auth-cache: mah.everybody.org is NXDOMAIN
#vendor-branch: Link to the latest release of the book
#vendor-branch: lookfirst.com is NXDOMAIN
#bikeshed: Old link was 301, change to new location
#cvssv3: Update links to current anchors in the target page
Modified:
subversion/site/staging/faq.html
Modified: subversion/site/staging/faq.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/faq.html?rev=1910824&r1=1910823&r2=1910824&view=diff
==============================================================================
--- subversion/site/staging/faq.html (original)
+++ subversion/site/staging/faq.html Thu Jul 6 19:59:51 2023
@@ -2062,13 +2062,7 @@ OpenSSH keys and <b><tt>pageant</tt></b>
<p>Setting up <tt>ssh-agent</tt> is outside the scope of this
document, but a <a
href="https://www.google.com/search?hl=en&lr=&ie=UTF-8&q=%22ssh-agent%22";
->Google search for "ssh-agent"</a> will quickly get you answers. Or
-if you're <i>really</i> impatient, try this one:</p>
-
-<pre>
- <a href="http://mah.everybody.org/docs/ssh";
- >http://mah.everybody.org/docs/ssh</a>
-</pre>
+>Google search for "ssh-agent"</a> will quickly get you answers.</p>
</div>
@@ -2642,23 +2636,13 @@ divergent branch, while still incorporat
upstream source. This is commonly called a <em>vendor branch</em>
(the term long predates Subversion), and the techniques for
maintaining one in Subversion are <a
-href="https://svnbook.red-bean.com/en/1.4/svn-book.html#svn.advanced.vendorbr";
+href="https://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.vendorbr";
>described here</a>.</p>
<p>If the vendor code is hosted in a remote Subversion repository,
then you can use <a href="https://github.com/francois/piston";>Piston</a> to
manage your copy of the vendor's code.</p>
-<p>As a last resort, if using <tt>svn_load_dirs.pl</tt> is taking too
-much time or you're looking for the lazy solution, see also Jon
-Stevens' step-by-step explanation at <a
-href="https://lookfirst.com/2007/11/subversion-vendor-branches-howto.html";
->Subversion Vendor Branches Howto</a>. This solution does not make
-use of the space saving features in the Subversion backend when you
-copy new code over old code; in this solution, each import of a vendor
-code gets an entire new copy and there is no space savings for
-identical files.</p>
-
</div>
<div class="h3" id="undo">
@@ -4379,7 +4363,7 @@ to 1.9+ servers.</p>
title="Link to this section">¶</a>
</h3>
-<p>See Poul-Henning Kamp's post to freebsd-hackers: <a
href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING";>https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING</a>.
+<p>See Poul-Henning Kamp's post to freebsd-hackers: <a
href="https://docs.freebsd.org/en/books/faq/#bikeshed-painting";>https://docs.freebsd.org/en/books/faq/#bikeshed-painting</a>.
</p>
</div>
@@ -4471,12 +4455,12 @@ scoring lower and more risky vunerabilit
calculated by determining the metrics of the vunerability and then calculating
the score based on those metrics. If you want to understand how a score was
determined you would need the vector and an understanding of the
-<a
href="https://www.first.org/cvss/specification-document#8-CVSS-v3-0-Equations";
+<a href="https://www.first.org/cvss/specification-document#CVSS-v3-1-Equations";
>formula as specified by the standard</a>.
</p>
<p>The vector is an
-<a href="https://www.first.org/cvss/specification-document#6-Vector-String";
+<a href="https://www.first.org/cvss/specification-document#Vector-String";
>abbreviated description</a> of the metrics that apply to the vulnerability.
</p>
