Author: dsahlberg
Date: Sat Jun 26 21:20:51 2021
New Revision: 1891068
URL: http://svn.apache.org/viewvc?rev=1891068&view=rev
Log:
In site/staging:
Replace http:// with https:// links.
Replace some links where the original reply with 301/302 (link to new site)
or is lost (link through archive.org).
* contributing.html
* docs/community-guide/conventions.part.html
* docs/community-guide/general.part.html
* docs/community-guide/issues.part.html
* docs/community-guide/mailing-lists.part.html
* docs/community-guide/releasing.part.html
* docs/community-guide/roles.part.html
* docs/release-notes/index.html
* faq.html
* ideas.html
* news.html
* opw.html
* packages.html
* pronunciation/index.html
Modified:
subversion/site/staging/contributing.html
subversion/site/staging/docs/community-guide/conventions.part.html
subversion/site/staging/docs/community-guide/general.part.html
subversion/site/staging/docs/community-guide/issues.part.html
subversion/site/staging/docs/community-guide/mailing-lists.part.html
subversion/site/staging/docs/community-guide/releasing.part.html
subversion/site/staging/docs/community-guide/roles.part.html
subversion/site/staging/docs/release-notes/index.html
subversion/site/staging/faq.html
subversion/site/staging/ideas.html
subversion/site/staging/news.html
subversion/site/staging/opw.html
subversion/site/staging/packages.html
subversion/site/staging/pronunciation/index.html
Modified: subversion/site/staging/contributing.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/contributing.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/contributing.html (original)
+++ subversion/site/staging/contributing.html Sat Jun 26 21:20:51 2021
@@ -38,7 +38,7 @@
<ul>
<li><p style="font-weight: bold;">Participate in the mailing lists</p>
- <p>There are <a href="http://subversion.apache.org/faq#more-information";>
+ <p>There are <a href="https://subversion.apache.org/faq#more-information";>
mailing lists, IRC channels and forums</a>
you can join to discuss Subversion. These are an
excellent source for users and contributors interested in
@@ -168,7 +168,7 @@
software code doesn't write itself, and projects generally
really do want as many people as possible to help write that
code. The Subversion project is no different. We've accepted
- and applied <a href="http://www.red-bean.com/svnproject/contribulyzer/";
+ and applied <a href="https://www.red-bean.com/svnproject/contribulyzer/";
>countless patch contributions</a>, and we hope to always have
a constant stream of them. If you're a developer able to
contribute in this way, take a cruise through our
@@ -194,7 +194,7 @@
is an excellent way for users to ensure that planned new features are
designed from the very beginning to meet their use-cases and wishes,
while for larger features holding such a discussion is key to
establishing
- <a href="http://producingoss.com/en/social-infrastructure.html";
+ <a href="https://producingoss.com/en/social-infrastructure.html";
>consensus</a> before any coding takes place.</p>
</li>
Modified: subversion/site/staging/docs/community-guide/conventions.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/conventions.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/conventions.part.html
(original)
+++ subversion/site/staging/docs/community-guide/conventions.part.html Sat Jun
26 21:20:51 2021
@@ -1104,7 +1104,7 @@ out which ones they are.</p>
and parseable way. This allows us to write scripts to figure out who
has been actively contributing — and what they have
contributed — so we can <a
-href="http://www.red-bean.com/svnproject/contribulyzer/";>spot
+href="https://www.red-bean.com/svnproject/contribulyzer/";>spot
potential new committers quickly</a>. The Subversion project uses
human-readable but machine-parseable fields in log messages to
accomplish this.</p>
Modified: subversion/site/staging/docs/community-guide/general.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/general.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/general.part.html (original)
+++ subversion/site/staging/docs/community-guide/general.part.html Sat Jun 26
21:20:51 2021
@@ -131,10 +131,10 @@ don't annoy others, and don't become eas
<li><p>Delta Editors</p>
<p>Karl Fogel wrote a chapter for O'Reilly's 2007 book
- <a rel="nofollow" href="http://beautifulcode.oreillynet.com/";>
+ <a rel="nofollow"
href="https://www.oreilly.com/library/view/beautiful-code/9780596510046/";>
Beautiful Code: Leading Programmers Explain How They Think</a>
covering the design and use of
- <a
href="http://www.red-bean.com/kfogel/beautiful-code/bc-chapter-02.html";>
+ <a
href="https://www.red-bean.com/kfogel/beautiful-code/bc-chapter-02.html";>
Subversion's delta editor interface</a>.</p>
</li>
@@ -633,7 +633,7 @@ subversion/include/*.h</a> for doxygen e
title="Link to this section">¶</a>
</h3>
-<p>We use the <a href="http://www.doxygen.org/";>Doxygen</a> format for
+<p>We use the <a href="https://www.doxygen.nl/";>Doxygen</a> format for
public interface documentation. This means anything that goes in a
public header file. The generated documentation is <a
href="/docs/#api">published on the web site</a>
Modified: subversion/site/staging/docs/community-guide/issues.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/issues.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/issues.part.html (original)
+++ subversion/site/staging/docs/community-guide/issues.part.html Sat Jun 26
21:20:51 2021
@@ -471,7 +471,7 @@ separately.)</p>
</h4>
<p>We publish the list of previous security advisories at:
-<a
href="http://subversion.apache.org/security/#advisories";>http://subversion.apache.org/security/</a></p>
+<a
href="https://subversion.apache.org/security/#advisories";>https://subversion.apache.org/security/</a></p>
<p>We track in-progress issues in the PMC's private repository:
<tt>https://svn.apache.org/repos/private/pmc/subversion/security</tt></p>
Modified: subversion/site/staging/docs/community-guide/mailing-lists.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/mailing-lists.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/mailing-lists.part.html
(original)
+++ subversion/site/staging/docs/community-guide/mailing-lists.part.html Sat
Jun 26 21:20:51 2021
@@ -143,8 +143,8 @@ href="https://www.unicom.com/pw/reply-to
"Principle of Least Damage" and "Can't Find My Way Back Home"
sections. From time to time, someone posts asking why we don't set
the <tt>Reply-to</tt> header. Sometimes that person will mention <a
-href="http://marc.merlins.org/netrants/reply-to-useful.html";
->http://marc.merlins.org/netrants/reply-to-useful.html</a>, which
+href="https://marc.merlins.org/netrants/reply-to-useful.html";
+>https://marc.merlins.org/netrants/reply-to-useful.html</a>, which
gives arguments in favor of modifying the <tt>Reply-to</tt> field.
The list administrators are aware of both documents, and see that both
sides of the argument have merits, but in the end have chosen not to
Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Sat Jun 26
21:20:51 2021
@@ -1494,7 +1494,7 @@ developed.</p>
<a href="https://svn.apache.org/r1460176";>code search and replace</a>.
(This is also a good time to do other periodical housekeeping tasks
such as
- <a
href="http://www.red-bean.com/svnproject/contribulyzer/detail/http%253A%252F%252Fscan.coverity.com%252F.html";>static</a>
+ <a
href="https://www.red-bean.com/svnproject/contribulyzer/detail/http%253A%252F%252Fscan.coverity.com%252F.html";>static</a>
<a href="https://svn.apache.org/r1469608";>analysis</a>.)</p></li>
<li><p>Review new and changed APIs for design and style (e.g. Doxygen mark-up,
undocumented parameters, deprecation, public/private status, etc.).</p>
Modified: subversion/site/staging/docs/community-guide/roles.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/roles.part.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/roles.part.html (original)
+++ subversion/site/staging/docs/community-guide/roles.part.html Sat Jun 26
21:20:51 2021
@@ -66,10 +66,10 @@ patch post and what's not is part of sho
patches and other contributions in a <a href="<!--#echo
var="GUIDE_CONVENTIONS_PAGE" -->#crediting">special
crediting format</a>, which is then parsed to produce a
browser-friendly <a
-href="http://www.red-bean.com/svnproject/contribulyzer/";>contribution
+href="https://www.red-bean.com/svnproject/contribulyzer/";>contribution
list</a>, updated nightly. If you're thinking of proposing someone
for commit access and want to look over all their changes, that <a
-href="http://www.red-bean.com/svnproject/contribulyzer/";>contribution
+href="https://www.red-bean.com/svnproject/contribulyzer/";>contribution
list</a> might be the most convenient place to do it.</p>
</div> <!-- full-commit-access -->
Modified: subversion/site/staging/docs/release-notes/index.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/index.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/index.html (original)
+++ subversion/site/staging/docs/release-notes/index.html Sat Jun 26 21:20:51
2021
@@ -83,9 +83,9 @@ official support status for the various
<!--#include virtual="/upcoming.part.html" -->
-<p>See also <a
href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>trunk/CHANGES</a>,
where all significant-enough changes will summarized for each version by the
time it is released.</p>
+<p>See also <a
href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>trunk/CHANGES</a>,
where all significant-enough changes will summarized for each version by the
time it is released.</p>
-<p>The list above is generated daily by <a
href="http://svn.apache.org/repos/asf/subversion/site/tools/upcoming.py";>^/subversion/site/tools/upcoming.py</a>.
You could find the changes queued for another release line by running that
script in a working copy of, for example, the 1.10.x branch.</p>
+<p>The list above is generated daily by <a
href="https://svn.apache.org/repos/asf/subversion/site/tools/upcoming.py";>^/subversion/site/tools/upcoming.py</a>.
You could find the changes queued for another release line by running that
script in a working copy of, for example, the 1.10.x branch.</p>
</div> <!-- #upcoming-patch-release -->
Modified: subversion/site/staging/faq.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/faq.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/faq.html (original)
+++ subversion/site/staging/faq.html Sat Jun 26 21:20:51 2021
@@ -1007,8 +1007,8 @@ in MOVE and COPY requests, so you have t
<p>Some links on SSH port forwarding</p>
<ul>
-<li><a href="http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_11/index3.html";
->http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_11/index3.html</a></li>
+<li><a
href="https://web.archive.org/web/20150618070908/http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_11/index3.html";
+>http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_11/index3.html</a> (on
archive.org)</li>
<li><a
href="https://engineering.purdue.edu/ECN/Support/KB/Docs/SSHIntroductionToSSH";
>https://engineering.purdue.edu/ECN/Support/KB/Docs/SSHIntroductionToSSH</a></li>
</ul>
@@ -1111,7 +1111,7 @@ 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="http://www.coelho.net/svn-merge-repos.html";>svn-merge-repos.pl</a>
+<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>
@@ -2646,7 +2646,7 @@ manage your copy of the vendor's code.</
<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="http://lookfirst.com/2007/11/subversion-vendor-branches-howto.html";
+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
@@ -3151,7 +3151,7 @@ and <tt>ssleay32.dll</tt> are present in
installation directory if they are not there.</p>
<p>If this still does not resolve the problem, you should use a tool
-like <a href="http://www.dependencywalker.com/";>Dependency Walker</a>
+like <a href="https://www.dependencywalker.com/";>Dependency Walker</a>
on <tt>mod_dav_svn.so</tt> to see if there are any other unresolved
dependencies.</p>
Modified: subversion/site/staging/ideas.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/ideas.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/ideas.html (original)
+++ subversion/site/staging/ideas.html Sat Jun 26 21:20:51 2021
@@ -105,8 +105,8 @@ and the <a href="https://live.gnome.org/
<ul>
<li>Some experience with the C and Python programming languages.</li>
<li>Knowledge of open source documentation systems such as
- <a href="http://docbook.org/";>docbook</a> and
- <a href="http://mdocml.bsd.lv/";>mdoc</a>.</li>
+ <a href="https://docbook.org/";>docbook</a> and
+ <a href="https://mandoc.bsd.lv/";>mdoc</a>.</li>
<li>The ability to clearly explain technical concepts in written
English.</li>
</ul>
Modified: subversion/site/staging/news.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/news.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/news.html (original)
+++ subversion/site/staging/news.html Sat Jun 26 21:20:51 2021
@@ -472,7 +472,7 @@
<p>The Subversion community has decided to make a standard release every 6
months, with a Long-Term Support (LTS) release every 2 years, from now on. The
recent 1.10 release shall be considered to be an LTS release.</p>
<p>Please see
- <a href="http://subversion.apache.org/roadmap.html#release-planning";
+ <a href="https://subversion.apache.org/roadmap.html#release-planning";
>How We Plan Releases</a> for more details.</p>
</div> <!-- #news-20180622 -->
@@ -510,7 +510,7 @@
<a
href="https://lists.apache.org/thread.html/3be8f8da7e806db1e97491808dcbf8ab5bc5a4b108b201c1258f70e7@%3Cdev.subversion.apache.org%3E";>release
announcement</a> for more information about this release, and the
<a href="/docs/release-notes/1.10.html">release notes</a> and
- <a href="http://svn.apache.org/repos/asf/subversion/tags/1.10.0-rc2/CHANGES";>
+ <a
href="https://svn.apache.org/repos/asf/subversion/tags/1.10.0-rc2/CHANGES";>
change log</a> for information about what will eventually be
in the 1.10.0 release.</p>
@@ -532,7 +532,7 @@
<a
href="https://lists.apache.org/thread.html/b4a01f414ae1c18b8316ff1211795a32efb7c4b8479e92f633945692@%3Cdev.subversion.apache.org%3E";>release
announcement</a> for more information about this release, and the
<a href="/docs/release-notes/1.10.html">release notes</a> and
- <a href="http://svn.apache.org/repos/asf/subversion/tags/1.10.0-rc1/CHANGES";>
+ <a
href="https://svn.apache.org/repos/asf/subversion/tags/1.10.0-rc1/CHANGES";>
change log</a> for information about what will eventually be
in the 1.10.0 release.</p>
@@ -1433,7 +1433,7 @@
<p>This year's Subversion hackathon will be held from June 10 to
June 14 at the offices of <a rel="nofollow"
-href="http://www.elego.de/";>elego</a> in Berlin, Germany.</p>
+href="https://www.elegosoft.com/";>elego</a> in Berlin, Germany.</p>
<p>The Subversion developer community will meet in Berlin to finish
off preparations for the upcoming Subversion 1.8 release and kick off
@@ -1567,7 +1567,7 @@ with the goal of increasing involvement
Free and Open Source Software (FOSS)</a>.
See <a href="opw.html">this page</a> for more information.</p>
-<p><a href="http://www.elego.de/"; rel="nofollow">Elego Software Solutions</a>,
+<p><a href="https://www.elegosoft.com/"; rel="nofollow">Elego Software
Solutions</a>,
based in Berlin, Germany, has kindly offered to fund an internship position
with Apache Subversion as part of the Outreach Program for Women 2013.</p>
Modified: subversion/site/staging/opw.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/opw.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/opw.html (original)
+++ subversion/site/staging/opw.html Sat Jun 26 21:20:51 2021
@@ -27,7 +27,7 @@ Free and Open Source Software (FOSS)</a>
This page contains information about contributing to Apache Subversion
as part of this program.</p>
-<p><a href="http://www.elego.de/"; rel="nofollow">Elego Software Solutions</a>,
+<p><a href="https://www.elegosoft.com/"; rel="nofollow">Elego Software
Solutions</a>,
based in Berlin, Germany, has kindly offered to fund an internship position
with Apache Subversion as part of the Outreach Program for Women 2013.</p>
Modified: subversion/site/staging/packages.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/packages.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/packages.html (original)
+++ subversion/site/staging/packages.html Sat Jun 26 21:20:51 2021
@@ -265,8 +265,8 @@ $ zypper install subversion-server</pre>
See the <a href="https://www.apple.com/opensource/";
>open source section of Apple's web site</a> for more
information.</p></li>
-<li><p><a href="http://pdb.finkproject.org/pdb/package.php/svn";
- >Fink</a> (requires <a href="http://www.finkproject.org/";>Fink</a>;
maintained by
+<li><p><a href="https://pdb.finkproject.org/pdb/package.php/svn";
+ >Fink</a> (requires <a href="https://www.finkproject.org/";>Fink</a>;
maintained by
<a href="mailto:[email protected]";
>Christian Schaffner</a>)</p>
</li>
Modified: subversion/site/staging/pronunciation/index.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/pronunciation/index.html?rev=1891068&r1=1891067&r2=1891068&view=diff
==============================================================================
--- subversion/site/staging/pronunciation/index.html (original)
+++ subversion/site/staging/pronunciation/index.html Sat Jun 26 21:20:51 2021
@@ -19,7 +19,7 @@
<h1>How To Pronounce "Subversion"</h1>
-<p><a href="http://www.red-bean.com/jimb/";>Jim Blandy</a>, who
+<p><a href="https://www.red-bean.com/jimb/";>Jim Blandy</a>, who
gave <a href="/">Subversion</a> both its
name and repository design, pronounces "Subversion" for posterity's
sake. Or something.</p>
