Author: luke1410
Date: Fri Dec 1 22:34:50 2017
New Revision: 1816924
URL: http://svn.apache.org/viewvc?rev=1816924&view=rev
Log:
* site/publish: Merge from staging.
Modified:
subversion/site/publish/ (props changed)
subversion/site/publish/contributing.html
subversion/site/publish/docs/community-guide/building.part.html
subversion/site/publish/docs/community-guide/conventions.part.html
subversion/site/publish/docs/community-guide/debugging.part.html
subversion/site/publish/docs/community-guide/general.part.html
subversion/site/publish/docs/community-guide/issues.part.html
subversion/site/publish/docs/community-guide/l10n.part.html
subversion/site/publish/docs/community-guide/mailing-lists.part.html
subversion/site/publish/docs/community-guide/releasing.part.html
subversion/site/publish/docs/community-guide/roles.part.html
subversion/site/publish/docs/community-guide/web.part.html
subversion/site/publish/docs/index.html
subversion/site/publish/docs/release-notes/1.1.html
subversion/site/publish/docs/release-notes/1.10.html
subversion/site/publish/docs/release-notes/1.2.html
subversion/site/publish/docs/release-notes/1.3.html
subversion/site/publish/docs/release-notes/1.4.html
subversion/site/publish/docs/release-notes/1.5.html
subversion/site/publish/docs/release-notes/1.6.html
subversion/site/publish/docs/release-notes/1.6.zh.html
subversion/site/publish/docs/release-notes/1.7.html
subversion/site/publish/docs/release-notes/1.8.html
subversion/site/publish/docs/release-notes/1.9.html
subversion/site/publish/docs/release-notes/index.html
subversion/site/publish/docs/release-notes/release-history.html
subversion/site/publish/download.html
subversion/site/publish/faq.html
subversion/site/publish/faq.ja.html
subversion/site/publish/faq.zh.html
subversion/site/publish/features.html
subversion/site/publish/ideas.html
subversion/site/publish/index.html (contents, props changed)
subversion/site/publish/mailing-lists.html
subversion/site/publish/news.html (contents, props changed)
subversion/site/publish/opw.html
subversion/site/publish/packages.html
subversion/site/publish/roadmap.html
subversion/site/publish/security/index.html
subversion/site/publish/site-banner.html
subversion/site/publish/site-nav.html
subversion/site/publish/source-code.html
Propchange: subversion/site/publish/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Dec 1 22:34:50 2017
@@ -1 +1 @@
-/subversion/site/staging:1815037-1815041,1815121-1815122,1815143,1816503,1816615
+/subversion/site/staging:1815037-1815041,1815121-1815122,1815143,1816503,1816509-1816580,1816615
Modified: subversion/site/publish/contributing.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/contributing.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/contributing.html (original)
+++ subversion/site/publish/contributing.html Fri Dec 1 22:34:50 2017
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
@@ -47,8 +47,8 @@
<li><p style="font-weight: bold;">Promote Subversion</p>
<p>Help promote Subversion by using your blog,
- <a href="http://twitter.com/"; >Twitter</a>,
- <a href="http://facebook.com/"; >Facebook</a>, or submitting an
+ <a href="https://twitter.com/"; >Twitter</a>,
+ <a href="https://facebook.com/"; >Facebook</a>, or submitting an
article to your favorite local magazine. If you are a member
of a different open source community, why not mention
Subversion on their discussion forums or at conferences? If you
@@ -61,8 +61,8 @@
<li><p style="font-weight: bold;">Link to subversion.apache.org</p>
<p>The success of any open source project depends on the number of
people who use the product and contribute back to the project.
- By linking to <a href="http://subversion.apache.org";
- >http://subversion.apache.org</a>, you increase the chances of
+ By linking to <a href="https://subversion.apache.org/";
+ >https://subversion.apache.org/</a>, you increase the chances of
a new user or contributor finding out about the project and
joining the community.</p>
</li>
@@ -188,7 +188,7 @@
involves discussions on the <a href="mailing-lists#dev-ml">dev@
list</a>, with reasonably detailed rationales and implementation plans
fly across the room. (We often <a
- href="http://wiki.apache.org/subversion/DesignNotes";>use our wiki</a>
+ href="https://wiki.apache.org/subversion/DesignNotes";>use our wiki</a>
to work on the proposed designs.) Participating in such a discussion
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,
Modified: subversion/site/publish/docs/community-guide/building.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/building.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/building.part.html (original)
+++ subversion/site/publish/docs/community-guide/building.part.html Fri Dec 1
22:34:50 2017
@@ -241,9 +241,9 @@ it again.</p>
<p>For a description of how to use and add tests to Subversion's
automated test framework, please read <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/README";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/README";
>subversion/tests/README</a> and <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/cmdline/README";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/cmdline/README";
>subversion/tests/cmdline/README</a>.</p>
</div> <!-- automated-tests -->
@@ -255,9 +255,9 @@ href="http://svn.apache.org/repos/asf/su
title="Link to this section">¶</a>
</h2>
-<p>The <a href="http://apache.org/dev/infrastructure.html";>ASF
+<p>The <a href="https://www.apache.org/dev/infrastructure.html";>ASF
Infrastructure</a> team manages
-a <a href="http://buildbot.net/";>BuildBot</a> build/test
+a <a href="https://buildbot.net/";>BuildBot</a> build/test
farm. The Buildbot waterfall for the Subversion project is located here:</p>
<ul>
<li><a href="/buildbot/prod">Production builds</a></li>
@@ -267,7 +267,7 @@ farm. The Buildbot waterfall for the Sub
<li><a href="/buildbot/all">The whole farm</a></li>
</ul>
<p>For more information about build services, head over
-to <a href="http://ci.apache.org";>ci.apache.org</a>.
+to <a href="https://ci.apache.org";>ci.apache.org</a>.
</p>
<p>If you'd like to receive notifications about buildbot build and
Modified: subversion/site/publish/docs/community-guide/conventions.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/conventions.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/conventions.part.html
(original)
+++ subversion/site/publish/docs/community-guide/conventions.part.html Fri Dec
1 22:34:50 2017
@@ -64,8 +64,8 @@ load svn-dev.el to get the right indenta
files here will load it automatically, if `enable-local-eval' is set
appropriately).</p>
-<p>Read <a href="http://www.gnu.org/prep/standards.html";
->http://www.gnu.org/prep/standards.html</a> for a full description of
+<p>Read <a href="https://www.gnu.org/prep/standards.html";
+>https://www.gnu.org/prep/standards.html</a> for a full description of
the GNU coding standards. Below is a short example demonstrating the
most important formatting guidelines, including our
no-space-before-param-list-paren exception:</p>
@@ -630,10 +630,10 @@ ensure correct destruction of the resour
it must correctly call the destructors of the stream(s) it is built
upon (owns).</p>
-<p>At first in <a href="http://svn.haxx.se/dev/archive-2005-12/0487.shtml";>
-http://svn.haxx.se/dev/archive-2005-12/0487.shtml</a>
-and later in <a href="http://svn.haxx.se/dev/archive-2005-12/0633.shtml";>
-http://svn.haxx.se/dev/archive-2005-12/0633.shtml</a> this
+<p>At first in <a href="https://svn.haxx.se/dev/archive-2005-12/0487.shtml";>
+https://svn.haxx.se/dev/archive-2005-12/0487.shtml</a>
+and later in <a href="https://svn.haxx.se/dev/archive-2005-12/0633.shtml";>
+https://svn.haxx.se/dev/archive-2005-12/0633.shtml</a> this
was discussed in more general terms for files, streams, editors and
window handlers.</p>
@@ -897,7 +897,7 @@ necessary. </p>
reading the rest of the log message, but also plays well with the
"ASFBot" bot that echoes the first line of each commit to realtime
forums like IRC. (For details, see
-<a href="http://wilderness.apache.org/";>http://wilderness.apache.org/</a>
+<a href="https://wilderness.apache.org/";>https://wilderness.apache.org/</a>
)</p>
<p> If the commit is just one simple change to one file, then you can
@@ -1127,7 +1127,7 @@ separate line — making sure t
line with whitespace. Non-committers should be listed by name, if
known, and e-mail. Full and partial committers should be listed by
their canonical usernames from <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/COMMITTERS";
+href="https://svn.apache.org/repos/asf/subversion/trunk/COMMITTERS";
>COMMITTERS</a> (the leftmost column in that file). Additionally,
"me" is an acceptable shorthand for the person actually committing the
change.</p>
Modified: subversion/site/publish/docs/community-guide/debugging.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/debugging.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/debugging.part.html (original)
+++ subversion/site/publish/docs/community-guide/debugging.part.html Fri Dec 1
22:34:50 2017
@@ -249,7 +249,7 @@ trace — see the <tt>http-comp
title="Link to this section">¶</a>
</h3>
-<p>Use <a href="http://www.wireshark.org/";>Wireshark</a> (formerly
+<p>Use <a href="https://www.wireshark.org/";>Wireshark</a> (formerly
known as "Ethereal") to eavesdrop on the conversation.</p>
<p>First, make sure that between captures within the same wireshark
@@ -346,8 +346,8 @@ with < and > signs to show the dir
</h3>
<p>If you're debugging a http client/server setup you can use a web
-debugging proxy like <a href="http://www.charlesproxy.com/";>Charles</a> or
-<a href="http://www.fiddler2.com/";>Fiddler</a>.</p>
+debugging proxy like <a href="https://www.charlesproxy.com/";>Charles</a> or
+<a href="https://www.fiddler2.com/";>Fiddler</a>.</p>
<p>Once you've setup such a proxy you'll need to configure Subversion to use
the
proxy. This can be done with the <tt>http-proxy-host</tt> and
<tt>http-proxy-port</tt>
Modified: subversion/site/publish/docs/community-guide/general.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/general.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Fri Dec 1
22:34:50 2017
@@ -14,7 +14,7 @@
<p>Although Subversion was originally sponsored and hosted by
CollabNet
-(<a rel="nofollow" href="http://www.collab.net";>http://www.collab.net</a>),
+(<a rel="nofollow" href="https://www.collab.net";>https://www.collab.net</a>),
it's a true open-source project under the Apache License, Version 2.0.
A number of Subversion's developers are paid by their employers to
improve Subversion, while many others are simply excellent volunteers
@@ -26,7 +26,7 @@ Subversion repository. To participate:<
<ul>
<li>
<p>Join us on irc.freenode.net #svn-dev or via the
-<a href="http://webchat.freenode.net/?nick=visitor....&channels=svn-dev";
+<a href="https://webchat.freenode.net/?nick=visitor....&channels=svn-dev";
>freenode IRC webchat interface.</a></p>
</li>
@@ -35,8 +35,8 @@ Subversion repository. To participate:<
discussion takes place. All development questions should go
there, though you might want to check the list archives first.
The "commits" list receives automated commit emails.
- See <a href="http://subversion.apache.org/mailing-lists.html";
- >http://subversion.apache.org/mailing-lists.html</a>
+ See <a href="https://subversion.apache.org/mailing-lists.html";
+ >https://subversion.apache.org/mailing-lists.html</a>
for details.</p></li>
<li><p>Get a copy of the latest development sources from
@@ -114,7 +114,7 @@ don't annoy others, and don't become eas
<ol>
<li><p>Design</p>
- <p>A <a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/subversion-design.html";
+ <p>A <a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/subversion-design.html";
>design spec</a> was written in June 2000, and is a bit out of
date. But it still gives a good theoretical introduction to the
inner workings of the repository, and to Subversion's various
@@ -137,13 +137,13 @@ don't annoy others, and don't become eas
<li> <p>Network Protocols</p>
- <p>The <a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-usage.html";
+ <p>The <a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-usage.html";
>WebDAV Usage</a> document is an introduction to Subversion's DAV
network protocol, which is an extended dialect of HTTP and uses
URLs beginning with "http://"; or "https://";.</p>
<p>The <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_ra_svn/protocol";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_ra_svn/protocol";
>SVN Protocol</a> document contains a formal description of
Subversion ra_svn network protocol, which is a custom protocol
on port 3690 (by default), whose URLs begin with "svn://" or
@@ -167,7 +167,7 @@ href="http://svn.apache.org/repos/asf/su
<p>A lot of the design ideas for particular aspects of the system
have been documented in individual files in the <a
- href="http://svn.apache.org/repos/asf/subversion/trunk/notes/";
+ href="https://svn.apache.org/repos/asf/subversion/trunk/notes/";
>notes/</a> directory.</p>
</li>
@@ -247,12 +247,12 @@ perusal order:</p>
</ol>
<p>Subversion tries to stay portable by using
-only the <a href="http://en.wikipedia.org/wiki/ANSI_C#C89_and_C90";>C89/C90</a>
-dialect of <a href="http://en.wikipedia.org/wiki/ANSI_C";>ANSI/ISO C</a> and
+only the <a href="https://en.wikipedia.org/wiki/ANSI_C#C89_and_C90";>C89/C90</a>
+dialect of <a href="https://en.wikipedia.org/wiki/ANSI_C";>ANSI/ISO C</a> and
by using the Apache Portable Runtime (APR) library. APR is the
portability layer used by the Apache httpd server, and more
-information can be found at <a href="http://apr.apache.org/";
->http://apr.apache.org/</a>.</p>
+information can be found at <a href="https://apr.apache.org/";
+>https://apr.apache.org/</a>.</p>
<p>Because Subversion depends so heavily on APR, it may be hard to
understand Subversion without first glancing over certain header files
@@ -283,7 +283,7 @@ in the C programming language. Please se
the full rationale behind this. Specifically, you should make it a
point to carefully read David Wheeler's Secure Programming (as
mentioned in
-<a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/assurance.txt";>
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/assurance.txt";>
'notes/assurance.txt'</a>). If at any point you have
questions about the security implications of a change, you are urged
to ask for review on the developer mailing list.</p>
@@ -465,7 +465,7 @@ enough to go on trunk, then create a tem
There's no need to ask — just do it. It's fine to try
out experimental ideas in a temporary branch, too. And all the
preceding applies to partial as well as full committers. It even
-applies to committers of other <a href="http://www.apache.org";>ASF</a>
+applies to committers of other <a href="https://www.apache.org";>ASF</a>
projects, but please talk to us (on dev@)—introduce yourself
and the problem you plan to work on.</p>
@@ -618,7 +618,7 @@ comments should help understanding of th
<p>Read over the Subversion code to get an overview of how documentation looks
in practice; in particular, see
-<a href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/include/";>
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/include/";>
subversion/include/*.h</a> for doxygen examples.
</p>
@@ -637,7 +637,7 @@ href="http://subversion.apache.org/docs/
for the latest and some earlier Subversion sources.</p>
<p>We use only a small portion of the available
-<a href="http://www.stack.nl/~dimitri/doxygen/commands.html";>doxygen
+<a href="https://www.stack.nl/~dimitri/doxygen/commands.html";>doxygen
commands</a> to markup our source. When writing doxygen documentation, the
following conventions apply:</p>
<ul>
@@ -655,7 +655,7 @@ following conventions apply:</p>
together using <code>@defgroup</code> and <code>@{...@}</code>.</li>
</ul>
-<p>See the <a href="http://www.stack.nl/~dimitri/doxygen/manual.html";>Doxygen
+<p>See the <a href="https://www.stack.nl/~dimitri/doxygen/manual.html";>Doxygen
manual</a> for a complete list of commands.</p>
</div> <!-- doxygen-docs -->
Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Fri Dec 1
22:34:50 2017
@@ -195,8 +195,8 @@ make the bug much more likely to get fix
>[email protected]</a>.
The Apache httpd developer mailing list is high-traffic, so your
bug report post has the possibility to be overlooked. You may also
- file a bug report at <a href="http://httpd.apache.org/bug_report.html";
- >http://httpd.apache.org/bug_report.html</a>.</p></li>
+ file a bug report at <a href="https://httpd.apache.org/bug_report.html";
+ >https://httpd.apache.org/bug_report.html</a>.</p></li>
<li><p>If the bug is in your rug, please give it a hug and keep it
snug.</p></li>
@@ -425,7 +425,7 @@ third-party libraries and APIs they prov
<p>This document describes the steps we take when receiving or finding an
issue which may be classified as having security implications, and is meant to
suppliment the
-<a href="http://www.apache.org/security/committers.html";>Apache guidelines</a>
+<a href="https://www.apache.org/security/committers.html";>Apache guidelines</a>
to committers for the same.</p>
<!-- Some thoughts about what to put here:
Modified: subversion/site/publish/docs/community-guide/l10n.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/l10n.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/l10n.part.html (original)
+++ subversion/site/publish/docs/community-guide/l10n.part.html Fri Dec 1
22:34:50 2017
@@ -9,7 +9,7 @@
<p>Translation has been divided into two domains. First, there is the
translation of server messages sent to connecting clients. This issue
has been <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/l10n-problems";
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/l10n-problems";
>punted for now</a>. Second there is the translation of the client and its
libraries.</p>
@@ -60,14 +60,14 @@ locale being written as any form of prog
<p>The GNU gettext manual
(<a
-href="http://www.gnu.org/software/gettext/manual/html_node/gettext_toc.html";
->http://www.gnu.org/software/gettext/manual/html_node/gettext_toc.html</a>)
+href="https://www.gnu.org/software/gettext/manual/html_node/gettext_toc.html";
+>https://www.gnu.org/software/gettext/manual/html_node/gettext_toc.html</a>)
provides additional information on writing translatable programs in
its section "Preparing Program Sources". Its hints mainly apply to
string composition.</p>
<p>Currently available translations can be found in <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/po/";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/po/";
>the po section of the repository</a>. Please contact
[email protected] when you want to start a translation not
available yet. Translation discussion takes place both on that list
Modified: subversion/site/publish/docs/community-guide/mailing-lists.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/mailing-lists.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/mailing-lists.part.html
(original)
+++ subversion/site/publish/docs/community-guide/mailing-lists.part.html Fri
Dec 1 22:34:50 2017
@@ -138,8 +138,8 @@ instead.)</p>
<tt>Reply-to</tt> header to redirect responses to the list. They
leave <tt>Reply-to</tt> set to whatever the original sender had, for
the reasons listed in <a
-href="http://www.unicom.com/pw/reply-to-harmful.html";
->http://www.unicom.com/pw/reply-to-harmful.html</a>, in particular the
+href="https://www.unicom.com/pw/reply-to-harmful.html";
+>https://www.unicom.com/pw/reply-to-harmful.html</a>, in particular the
"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
@@ -225,8 +225,8 @@ not a major inconvenience even when done
<p>If you came here looking for advice on how to quote, instead of
advice on how to not flame people for their bad quoting habits, see <a
-href="http://www.netmeister.org/news/learn2quote.html";
->http://www.netmeister.org/news/learn2quote.html</a> (Deutsch:
+href="https://www.netmeister.org/news/learn2quote.html";
+>https://www.netmeister.org/news/learn2quote.html</a> (Deutsch:
<a href="http://learn.to/quote";>http://learn.to/quote</a>).</p>
</div> <!-- top-posting -->
@@ -243,8 +243,8 @@ href="http://www.netmeister.org/news/lea
<p>See <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches">here</a> for
advice on how to send in a
patch. Note that you can send in a patch to modify these web pages as
well as to modify code; the web pages' repository URL is
-<a href="http://svn.apache.org/repos/asf/subversion/site/";
->http://svn.apache.org/repos/asf/subversion/site/</a>.</p>
+<a href="https://svn.apache.org/repos/asf/subversion/site/";
+>https://svn.apache.org/repos/asf/subversion/site/</a>.</p>
</div> <!-- sending-patches -->
Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Dec 1
22:34:50 2017
@@ -21,14 +21,14 @@ order of specificity:</p>
</ul>
<p>Subversion release managers use a set of steps codified in a Python script
-named <a
href="http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py";><tt>release.py</tt></a>.
+named <a
href="https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py";><tt>release.py</tt></a>.
This script can be used to perform most of the automated steps
in the release process. Run it with the <tt>-h</tt> option to get more
information.</p>
<p>In addition to the following project-specific guidelines, aspiring release
managers may also want to read up on the general
-<a href="http://www.apache.org/dev/release.html";>Apache release policies</a>.
+<a href="https://www.apache.org/dev/release.html";>Apache release policies</a>.
They can seem a bit patchwork at times, but give a good idea of general
best practice and how Subversion fits in the larger ASF ecosystem.</p>
@@ -123,7 +123,7 @@ reports.</p>
<p>We also produce a set of release-like tarballs from the trunk development
line
-<a href="http://ci.apache.org/projects/subversion/nightlies/index.html";>every
+<a href="https://ci.apache.org/projects/subversion/nightlies/index.html";>every
night</a>, but these have no testing and are only recommended for users
looking to run the bleeding edge, or test a particular bug fix, without
building directly from the repository.</p>
@@ -221,8 +221,8 @@ remain in the repository history, but th
</h3>
<p>Subversion follows strict compatibility, with the same
-guidelines as APR (see <a href="http://apr.apache.org/versioning.html";
->http://apr.apache.org/versioning.html</a>), plus a few extensions,
+guidelines as APR (see <a href="https://apr.apache.org/versioning.html";
+>https://apr.apache.org/versioning.html</a>), plus a few extensions,
described later. These guidelines are in place to ensure various forms of
client/server interoperability, and make sure users have a clear upgrade
path between MAJOR.MINOR Subversion releases.</p>
@@ -252,7 +252,7 @@ to the greatest extent possible. The ge
<p>(Occasionally, bugs are found which require the behavior of old APIs
to be modified slightly. This typically only manifests itself in
various corner cases and other uncommon area. These changes are
- documented as <a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/";>API
errata</a> for each MAJOR.MINOR release.)</p>
+ documented as <a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/";>API
errata</a> for each MAJOR.MINOR release.)</p>
</li>
<li><p>When the major number changes, all bets are off. This is the
@@ -365,7 +365,7 @@ your distribution and the official Subve
possible.</p>
<p>First, make sure you follow the <a
-href="http://www.apache.org/foundation/marks/";>ASF
+href="https://www.apache.org/foundation/marks/";>ASF
trademark policy</a>. You will need to differentiate your release
from the standard Subversion releases to reduce any potential
confusion caused by your custom release.</p>
@@ -934,13 +934,13 @@ the dev@ list.</p>
</h3>
<p>Because Subversion releases are distributed through the
-<a href="http://www.apache.org/dev/mirrors.html";>ASF mirror network</a>, it
+<a href="https://www.apache.org/dev/mirrors.html";>ASF mirror network</a>, it
is important that end-users be able to verify the authenticity of the source
code packages they download. Checksums are sufficient to detect corruption
in the download process, but to prevent a malicious individual or mirror
operator from distributing replacement packages, each source code package
must be
-<a href="http://www.apache.org/dev/release-signing.html";>cryptographically
+<a href="https://www.apache.org/dev/release-signing.html";>cryptographically
signed</a> by members of the Subversion PMC. These
signatures are done using each committer's private PGP key, and are then
published with the release so that end users can verify the integrity of the
@@ -994,7 +994,7 @@ automates this step:
<p>After having verified, extracted, and tested the tarball,
you should sign by creating
-an armored detached signature using <a href="http://www.gnupg.org";>gpg</a>.
+an armored detached signature using <a href="https://www.gnupg.org";>gpg</a>.
To append your signature to a .asc file, use a command like:</p>
<pre>
gpg -ba -o - subversion-1.7.0-rc4.tar.bz2 >>
subversion-1.7.0-rc4.tar.bz2.asc
@@ -1041,12 +1041,12 @@ validated, the release is ready for publ
steps needed to publish a Subversion release.</p>
<p>Subversion artifacts are distributed through the
-<a href="http://www.apache.org/dev/mirrors.html";>ASF mirror network</a>. The
+<a href="https://www.apache.org/dev/mirrors.html";>ASF mirror network</a>. The
source code <a href="/download.cgi">download page</a> automatically assists
users
in selecting mirrors closer to them. We usually host only the latest stable
release for the supported release lines on the mirror network, while all
previous Subversion releases are available in the
-<a href="http://archive.apache.org/dist/subversion/";>archives</a>.</p>
+<a href="https://archive.apache.org/dist/subversion/";>archives</a>.</p>
<p>Uploading releases to the mirrors is rather straight forward: the RM simply
moves the tarballs, signatures and checksums from
@@ -1214,18 +1214,18 @@ A.B with the version you're preparing, e
<li><p>Do any tree-wide, mechanical changes. (Non-mechanical changes should
have happened earlier to allow for review.) This eases merging later.
Examples include
- <a href="http://svn.apache.org/r1467191";>stripping trailing
whitespace</a>
+ <a href="https://svn.apache.org/r1467191";>stripping trailing
whitespace</a>
and
- <a href="http://svn.apache.org/r1467261";>plugging error leaks</a>
+ <a href="https://svn.apache.org/r1467261";>plugging error leaks</a>
and
- <a href="http://svn.apache.org/r1466965";>fixing invariants in C
headers</a>
- (<a href="http://svn.apache.org/r1546937";>another case</a>)
+ <a href="https://svn.apache.org/r1466965";>fixing invariants in C
headers</a>
+ (<a href="https://svn.apache.org/r1546937";>another case</a>)
and
- <a href="http://svn.apache.org/r1460176";>code search and replace</a>.
+ <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="http://svn.apache.org/r1469608";>analysis</a>.)</p></li>
+ <a href="https://svn.apache.org/r1469608";>analysis</a>.)</p></li>
<li><p>Create the new release branch with a server-side copy:</p>
<pre>
svn cp ^/subversion/trunk \
@@ -1242,7 +1242,7 @@ A.B with the version you're preparing, e
the 1.3.x branch).</p></li>
<li><p>Edit
<tt>/subversion/trunk/subversion/bindings/javahl/src/org/apache/subversion/javahl/NativeResources.java</tt>
on trunk and
- <a href="http://svn.apache.org/r1483917";>increment the version numbers in
+ <a href="https://svn.apache.org/r1483917";>increment the version numbers in
<tt>init()</tt></a>. Do not commit these changes yet.</p></li>
<li><p>Edit <tt>build/run_tests.py</tt> and
@@ -1257,7 +1257,7 @@ A.B with the version you're preparing, e
<pre>
Version A.B.0
(?? ??? 20XX, from /branches/A.B.x)
- http://svn.apache.org/repos/asf/subversion/tags/A.B.0
+ https://svn.apache.org/repos/asf/subversion/tags/A.B.0
</pre>
<p>Leave the release date blank for now. It will remain this way
until rolling time.</p></li>
Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Fri Dec 1
22:34:50 2017
@@ -22,7 +22,7 @@ specific area(s) of expertise. While ev
regardless of its source, not every person who contributes code to
Subversion will earn commit access.</p>
-<p>The <a href="http://svn.apache.org/repos/asf/subversion/trunk/COMMITTERS";
+<p>The <a href="https://svn.apache.org/repos/asf/subversion/trunk/COMMITTERS";
>COMMITTERS</a> file lists all committers, both full and partial, and
says the domains for each partial committer.</p>
@@ -184,7 +184,7 @@ Obvious fix.
<p>Subversion is part of the <acronym title="Apache Software
Foundation">ASF</acronym>, and shares the same repository with 100+ other
-ASF <a href="http://projects.apache.org/";>projects</a>. While people who
+ASF <a href="https://projects.apache.org/";>projects</a>. While people who
are committers on those projects are not considered either full or partial
committers to Subversion, they are welcome to commit
<a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#obvious-fix">obvious fixes</a>,
Modified: subversion/site/publish/docs/community-guide/web.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/web.part.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/web.part.html (original)
+++ subversion/site/publish/docs/community-guide/web.part.html Fri Dec 1
22:34:50 2017
@@ -68,9 +68,9 @@
any changes you might wish to make, you need to view the relevant
pages through a web browser connected to a server installed on your
system, either
- <a href="http://httpd.apache.org/docs/2.2/install.html";>Apache 2.2</a>
+ <a href="https://httpd.apache.org/docs/2.2/install.html";>Apache 2.2</a>
or
- <a href="http://httpd.apache.org/docs/2.4/install.html";>Apache 2.4</a>.
+ <a href="https://httpd.apache.org/docs/2.4/install.html";>Apache 2.4</a>.
</p>
@@ -155,7 +155,7 @@ you've changed with
</pre>
</p>
<p>then upload the resulting file to a HTML validator, for
-example, <a href="http://validator.w3.org/";>W3C validator service</a>.
+example, <a href="https://validator.w3.org/";>W3C validator service</a>.
</div> <!-- web_validation -->
@@ -169,7 +169,7 @@ example, <a href="http://validator.w3.or
<p>
When writing log messages for patches regarding the project's web pages, eg:
</p>
-<pre>http://subversion.apache.org/docs/community-guide/some_page.html#section-name
+<pre>https://subversion.apache.org/docs/community-guide/some_page.html#section-name
</pre>
<p> list the names of files modified in the patch in the log message,
relative to the <code>site/</code> directory and list anchors of
Modified: subversion/site/publish/docs/index.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/index.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/index.html (original)
+++ subversion/site/publish/docs/index.html Fri Dec 1 22:34:50 2017
@@ -33,7 +33,7 @@
<p>If you want to know how to use Subversion, you can find a number of
published user manuals available
- for <a
href="http://www.google.com/search?q=site%3Aamazon.com+Subversion+version+control";
+ for <a
href="https://www.google.com/search?q=site%3Aamazon.com+Subversion+version+control";
>purchase</a> online. One of these texts
— <span style="font-style: italic;" >Version Control With
Subversion</span> (affectionately known as "the Subversion book")
@@ -128,12 +128,12 @@
<ul>
<li>
- <a href="http://people.apache.org/~brane/svndocs/capi/";>C API</a>
- (<a href="http://people.apache.org/~brane/svndocs/capi.build.log";>build
log</a>)
+ <a href="https://people.apache.org/~brane/svndocs/capi/";>C API</a>
+ (<a href="https://people.apache.org/~brane/svndocs/capi.build.log";>build
log</a>)
</li>
<li>
- <a href="http://people.apache.org/~brane/svndocs/javahl/";>JavaHL</a>
- (<a href="http://people.apache.org/~brane/svndocs/javahl.build.log";>build
log</a>)
+ <a href="https://people.apache.org/~brane/svndocs/javahl/";>JavaHL</a>
+ (<a href="https://people.apache.org/~brane/svndocs/javahl.build.log";>build
log</a>)
</li>
</ul>
Modified: subversion/site/publish/docs/release-notes/1.1.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.1.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.1.html (original)
+++ subversion/site/publish/docs/release-notes/1.1.html Fri Dec 1 22:34:50 2017
@@ -83,8 +83,8 @@ a quick summary:</p>
repository over a network filesystem, and no more database "wedges"
needing recovery. You can read the full list of
advantages/disadvantages at <a
- href="http://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs";
- >http://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs</a></p>
+ href="https://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs";
+ >https://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs</a></p>
<p>To create an fsfs repository, simply run <tt>'svnadmin create
--fs-type fsfs'</tt>. Or, if BerkeleyDB wasn't detected at
@@ -139,7 +139,7 @@ feature</em>)</h4>
</pre>
<p>The definition of an Internationalized URI (IRI) is still a work in
progress; see <a
- href="http://www.w3.org/International/iri-edit/";>the draft spec</a>.</p>
+ href="https://www.w3.org/International/iri-edit/";>the draft spec</a>.</p>
@@ -186,7 +186,7 @@ server certificates can still be remembe
<h4>Bugfixes:</h4>
<p>More than 40 "small" bugs fixed. See the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
<h4>New subcommand switches:</h4>
@@ -242,7 +242,7 @@ href="http://svn.apache.org/repos/asf/su
suffix, and the older versions are now marked deprecated (and will be
removed in Subversion 2.0). For example, a new svn_wc_diff2()
function has superseded svn_wc_diff(). See the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
<p>There has been extensive work on the python, perl, and java
@@ -253,7 +253,7 @@ swig-py' or 'make swig-pl' or 'make java
<h3>Testimonials and Roadmap</h3>
-<p>See our <a href="roadmap.html">roadmap</a> for what the future
+<p>See our <a href="/roadmap.html">roadmap</a> for what the future
looks like.</p>
<p>If you're looking for testimonials on Subversion, see our new <a
Modified: subversion/site/publish/docs/release-notes/1.10.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.10.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.10.html (original)
+++ subversion/site/publish/docs/release-notes/1.10.html Fri Dec 1 22:34:50
2017
@@ -59,7 +59,7 @@ earlier release. The new features will
<p>This page describes only major changes. For a complete list of
changes, see the 1.10 section of the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
file.</p>
</div> <!-- news -->
@@ -100,7 +100,7 @@ cannot necessarily compile or run agains
slightly modified from previous releases. These are cases where edge cases
of the functionality has been deemed buggy, and therefore improved or removed.
Please consult the
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.10/";
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.10/";
>API errata</a> for more detailed information on what these APIs are
and what impact these changes may have.</p>
@@ -720,9 +720,9 @@ capability.</p>
<p>mod_dav_svn servers now advertise this specific (new) capability.<p>
-<p>Ref. <a href="http://svn.apache.org/r1704317";>r1704317</a>,
-<a href="http://svn.apache.org/r1704891";>r1704891</a>,
-<a href="http://svn.apache.org/r1791290";>r1791290</a>. </p>
+<p>Ref. <a href="https://svn.apache.org/r1704317";>r1704317</a>,
+<a href="https://svn.apache.org/r1704891";>r1704891</a>,
+<a href="https://svn.apache.org/r1791290";>r1791290</a>. </p>
</div> <!-- serf-svndiff -->
Modified: subversion/site/publish/docs/release-notes/1.2.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.2.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.2.html (original)
+++ subversion/site/publish/docs/release-notes/1.2.html Fri Dec 1 22:34:50 2017
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
@@ -245,7 +245,7 @@ happily issue http LOCK and UNLOCK reque
opened/edited directly from the share. As far as we can tell,
mod_dav_svn is now fully implementing the 'autoversioning' feature
according to the <a
-href="http://greenbytes.de/tech/webdav/#draft-ietf-webdav-rfc2518bis";>RFC2518bis</a>
+href="https://greenbytes.de/tech/webdav/#draft-ietf-webdav-rfc2518bis";>RFC2518bis</a>
specification.</p>
<p>In informal tests, we've had success reading and writing to
@@ -413,7 +413,7 @@ password when necessary.</p>
title="Link to this section">¶</a>
</h3>
<p>More than 50 new bugs fixed. See the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
</div>
@@ -436,9 +436,9 @@ making svn_ra.h available via SWIG. </p>
<p>As with svn 1.1, a number of new 1.2 functions have been
introduced, and older versions are now marked deprecated (and will be
removed in Subversion 2.0). See the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details. The full list of new 1.2 APIs is <a
-href="http://svn.haxx.se/dev/archive-2005-04/0319.shtml";>here</a>.</p>
+href="https://svn.haxx.se/dev/archive-2005-04/0319.shtml";>here</a>.</p>
<p>There has been extensive work on the Python, Perl, and JavaHL
bindings. We also now have a preliminary set of Ruby bindings.</p>
Modified: subversion/site/publish/docs/release-notes/1.3.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.3.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.3.html (original)
+++ subversion/site/publish/docs/release-notes/1.3.html Fri Dec 1 22:34:50 2017
@@ -218,7 +218,7 @@ authz-db = authzfile
<p>To activate this new feature, you need to make use of httpd 2.0's
built in logging directives such
-as <a href="http://httpd.apache.org/docs/2.0/logs.html";>LogFormat and
+as <a href="https://httpd.apache.org/docs/2.0/logs.html";>LogFormat and
CustomLog</a> directives. These directives allow you to flexibly
define your own log formats. All you need to know is that mod_dav_svn
now sets an environment variable named SVN-ACTION whenever it feels
@@ -338,7 +338,7 @@ language bindings</em>)
<p>The "<b>_svn</b>" hack is
now <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/asp-dot-net-hack.txt";>officially
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/asp-dot-net-hack.txt";>officially
supported</a>: since some versions of ASP.NET don't allow directories
beginning with dot (e.g., ".svn", the standard Subversion working copy
administrative directory), the <b>svn</b> command line client
@@ -415,7 +415,7 @@ href="http://subversion.tigris.org/servl
</h3>
<p>The usual slew of heretofore-unreleased bugfixes. See the
-<a href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
+<a href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file for full details.</p>
</div> <!-- bugfixes -->
@@ -439,7 +439,7 @@ the only project that we know of that fa
they have been notified accordingly. If you happen to be using or
developing software that, similarly, bypasses the Subversion APIs,
then you may need to make a minor alteration to the parsing routines.
-See <a href="http://svn.apache.org/r856929";>revision 16855</a> of
+See <a href="https://svn.apache.org/r856929";>revision 16855</a> of
the Subversion repository for details.</p>
</div> <!-- wc-props-change -->
Modified: subversion/site/publish/docs/release-notes/1.4.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.4.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.4.html (original)
+++ subversion/site/publish/docs/release-notes/1.4.html Fri Dec 1 22:34:50 2017
@@ -129,7 +129,7 @@ made to the output:</p>
</h3>
<p>A new tool — <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt";
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt";
><tt>svnsync</tt></a> — is now installed as part of the standard
distribution. This tool provides the ability to replicate history
from one repository to another. The replication can happen all at
@@ -294,7 +294,7 @@ The <tt>svnserve</tt> server can now be
allows svnserve to start automatically, at system boot time, without
having a user logged in and without the need for an external service
'wrapper' program. See <a
-href="http://svn.apache.org/repos/asf/subversion/tags/1.4.0/notes/windows-service.txt";><tt>notes/windows-service.txt</tt></a>
+href="https://svn.apache.org/repos/asf/subversion/tags/1.4.0/notes/windows-service.txt";><tt>notes/windows-service.txt</tt></a>
for information on setting up <tt>svnserve</tt> as a Windows service.
</div> <!-- svnserve -->
@@ -337,7 +337,7 @@ rather than in <tt>~/.subversion/auth/</
<p>The usual slew of heretofore-unreleased bugfixes, more than 40
overall. See the
-<a href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
+<a href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file for full details.</p>
</div> <!-- bugfixes -->
Modified: subversion/site/publish/docs/release-notes/1.5.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.5.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.5.html (original)
+++ subversion/site/publish/docs/release-notes/1.5.html Fri Dec 1 22:34:50 2017
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
@@ -215,7 +215,7 @@ copies.)</p>
<p>If you accidentally upgrade a 1.4 working copy to 1.5, and wish to
downgrade back to 1.4, use the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py";
+href="https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py";
><tt>change-svn-wc-format.py</tt></a> script. See <a
href="/faq.html#working-copy-format-change"
>this FAQ entry</a> for details, and run the script with the
@@ -242,7 +242,7 @@ part of the repository admin.)</p>
<p>After running <strong><code>svnadmin upgrade</code></strong>,
you may wish to also run the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/tools/server-side/svn-populate-node-origins-index.c";
+href="https://svn.apache.org/repos/asf/subversion/trunk/tools/server-side/svn-populate-node-origins-index.c";
>svn-populate-node-origins-index</a> program on the repository.
Subversion 1.5 maintains a node-origins index for each repository, and
builds the index lazily as the information is needed. But for old
@@ -368,7 +368,7 @@ afterwards. In the meantime:</p>
href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.finalword";
>"The Final Word on Merge Tracking"</a> in the Subversion Book</p></li>
<li><p>Read <a
- href="http://www.collab.net/community/subversion/articles/merge-info.html";
+ href="https://www.collab.net/community/subversion/articles/merge-info.html";
>"Understanding the internals of Subversion's merge tracking feature"</a>
by Paul Burba</p></li>
</ul>
@@ -490,11 +490,11 @@ href="#repos-upgrades" >upgrade the repo
server.</p>
<p>If you were using the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/";
+href="https://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/";
>svnmerge</a> wrapper program to do merging, and now want to switch to
using Subversion 1.5's native merge-tracking, then you should use the
<a
-href="http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/svnmerge-migrate-history.py";
+href="https://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/svnmerge-migrate-history.py";
>svnmerge-migrate-history.py</a> script to convert svnmerge's custom
properties to the <tt>svn:mergeinfo</tt> properties that Subversion
itself now uses.</p>
@@ -759,7 +759,7 @@ this alleviates some of the extra networ
>Sparse Directories</a> section in the Subversion book.
</li>
<li>The <a
-
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/sparse-directories.txt";
+
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/sparse-directories.txt";
>design/implementation document</a> in the repository.</li>
</ul>
@@ -885,7 +885,7 @@ subcommands:</p>
>Changelists</a> section in the Subversion book.
</li>
<li>The <a
-
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/changelist-design.txt";
+
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/changelist-design.txt";
>design/implementation document</a> in the repository.</li>
</ul>
@@ -1067,7 +1067,7 @@ and server</em>)
</h3>
<p>From <a
-href="http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer";>
+href="https://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer";>
Wikipedia</a>: "SASL is a framework for authentication and data security in
Internet protocols. It decouples authentication mechanisms from application
protocols, in theory allowing any authentication mechanism supported by SASL to
@@ -1096,7 +1096,7 @@ mechanisms separately from the core libr
section</a> for information regarding using a 1.5 SASL-enabled server
with pre-1.5 clients. More information about Subversion's SASL
support can be found in <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/sasl.txt";
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/sasl.txt";
>sasl.txt</a>.</p>
</div> <!-- cyrus-sasl -->
@@ -1123,7 +1123,7 @@ become slower and common administrative
listings, backups) become unwieldy or fail completely.</p>
<p>For more information about the technical underpinnings of FSFS sharding,
-see this <a href="http://www.farside.org.uk/200704/tree_structured_fsfs";>blog
+see this <a href="https://www.farside.org.uk/200704/tree_structured_fsfs";>blog
entry</a>.
<!-- ### Reshard script is not quite finished and currently
### aborts if you try to run it.
@@ -1281,7 +1281,7 @@ held — but locking will
</h4>
<p>Additional information about WebDAV proxy support is available <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-proxy";>in
the
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-proxy";>in
the
repository</a>.</p>
</div> <!-- webdav-proxy-further-reading -->
@@ -1464,7 +1464,7 @@ actually stop.</p>
command-line client to list them all here. Aside from all the ones
mentioned already in these release notes, below are a few more that we
consider important, but please see the 1.5.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for a complete list.</p>
<div class="h4" id="resolve">
@@ -1589,7 +1589,7 @@ some may lag more than others.</p>
</h3>
<p>A great many bugs have been fixed. See the 1.5.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
</div> <!-- bug-fixes -->
Modified: subversion/site/publish/docs/release-notes/1.6.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.6.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.6.html (original)
+++ subversion/site/publish/docs/release-notes/1.6.html Fri Dec 1 22:34:50 2017
@@ -65,7 +65,7 @@ earlier release. The new features will
<p>This page describes only major changes. For a complete list of
changes, see the 1.6 section of the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
file.</p>
</div> <!-- news -->
@@ -162,7 +162,7 @@ copies.)</p>
<p>If you accidentally upgrade a 1.5 working copy to 1.6, and wish to
downgrade back to 1.5, use the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py";
+href="https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py";
><tt>change-svn-wc-format.py</tt></a> script. See <a
href="/faq.html#working-copy-format-change"
>this FAQ entry</a> for details, and run the script with the
@@ -381,7 +381,7 @@ Keyring, Mac OS Keychain, a Windows Cryp
<p><!-- XXX --><em>This section is currently incomplete, please
help write it!</em> See the
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/cli-repo-root-relative-support.txt";>design
notes</a> for more information.</p>
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/cli-repo-root-relative-support.txt";>design
notes</a> for more information.</p>
<pre>
$ svn SUBCOMMAND ^/
@@ -601,7 +601,7 @@ servers.</p>
title="Link to this section">¶</a>
</h4>
-<p><!-- XXX --><a href="http://www.danga.com/memcached/";>Memcached</a> can
+<p><!-- XXX --><a href="https://www.danga.com/memcached/";>Memcached</a> can
cache data of FSFS repositories.</p>
<p>Additional build-time dependencies: APR-Util ≥1.3 || ( APR-Util <
@@ -802,7 +802,7 @@ to work directly against repositories wi
command-line client to list them all here. Aside from all the ones
mentioned already in these release notes, below are a few more that we
consider important, but please see the 1.6.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for a complete list.</p>
<div class="h4" id="log-multiple-args">
@@ -921,7 +921,7 @@ some may lag more than others.</p>
</h3>
<p>A great many bugs have been fixed. See the 1.6.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
</div> <!-- bug-fixes -->
@@ -944,7 +944,7 @@ for details.</p>
compile when configured to include KDE wallet support. This can be
fixed by configuring without KDE wallet support, or by building with
an older GCC, or by patching
-with <a href="http://svn.apache.org/r1345740";>r1345740</a> from
+with <a href="https://svn.apache.org/r1345740";>r1345740</a> from
trunk. A fix is likely to be included in any future 1.6.x release.</p>
</div> <!-- kwallet-gcc-4.7 -->
@@ -959,7 +959,7 @@ trunk. A fix is likely to be included in
</p>
<ul>
<li>log_tests.py 30. This can be fixed by patching
- with <a href="http://svn.apache.org/r1293229";>r1293229</a> from
+ with <a href="https://svn.apache.org/r1293229";>r1293229</a> from
trunk.
</li>
<li>diff_tests.py 32 as the testsuite does not account for the
@@ -994,10 +994,10 @@ more 1.4.x bugfix releases.</p>
title="Link to this section">¶</a>
</h2>
-<p>We now require <a href="http://www.sqlite.org/";>SQLite</a> to build both
+<p>We now require <a href="https://www.sqlite.org/";>SQLite</a> to build both
the server and client. We recommend 3.6.13 or greater, but work with
anything better than 3.4.0. Subversion will attempt to use an SQLite
-<a href="http://www.sqlite.org/amalgamation.html";>amalgamation</a> if it is
+<a href="https://www.sqlite.org/amalgamation.html";>amalgamation</a> if it is
present in the root of the distribution tarball, otherwise, Subversion will
search for SQLite in the usual places on the system. You may also pass
<code>--with-sqlite</code> to <code>configure</code> to specify the location
Modified: subversion/site/publish/docs/release-notes/1.6.zh.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.6.zh.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.6.zh.html (original)
+++ subversion/site/publish/docs/release-notes/1.6.zh.html Fri Dec 1 22:34:50
2017
@@ -59,7 +59,7 @@
</p>
<p>æ¬ææè¿°äºä¸»è¦çåæ´ï¼å®æ´çå表å¯ä»¥ç<a
-href="http://svn.collab.net/repos/svn/trunk/CHANGES";
>CHANGES</a>ç1.6é¨åã</p>
+href="https://svn.collab.net/repos/svn/trunk/CHANGES";
>CHANGES</a>ç1.6é¨åã</p>
</div> <!-- news -->
@@ -461,7 +461,7 @@ href="http://svnbook.red-bean.com/nightl
title="Link to this section">¶</a>
</h4>
-<p>XXX: <a
href="http://www.danga.com/memcached/";>Memcached</a>å¯ä»¥ä¸ºFSFSçæ¬åºç¼åæ°æ®ã</p>
+<p>XXX: <a
href="https://www.danga.com/memcached/";>Memcached</a>å¯ä»¥ä¸ºFSFSçæ¬åºç¼åæ°æ®ã</p>
<p>é¢å¤çæ建ä¾èµï¼APR-Util ≥1.3 || ( APR-Util <
1.3 && APR_Memcache )</p>
@@ -741,8 +741,8 @@ href="http://svn.collab.net/repos/svn/tr
title="Link to this section">¶</a>
</h2>
-<p>æ们ç°å¨éè¦<a
href="http://www.sqlite.org/";>SQLite</a>æ¥æ建æå¡å¨å客æ·ç«¯ï¼æ们æ¨è3.6.13ææ´æ°ççæ¬ï¼ä½æ¯3.4.0å·²ç»è¶³å¤ãå¦æå®ä½äºtarballçæ
¹ä¸ï¼Subversionä¼å°è¯ä½¿ç¨SQLite
-<a
href="http://www.sqlite.org/amalgamation.html";>amalgamation</a>ï¼å¦åSubversionä¼å¨ç³»ç»ç常è§ä½ç½®å¯»æ¾SQLiteãä½
ä¹å¯ä»¥éè¿ä¼
éç»<code>configure</code>å½ä»¤<code>--with-sqlite</code>æ¥ææSQLiteåºæamalgamationçä½ç½®ã</p>
+<p>æ们ç°å¨éè¦<a
href="https://www.sqlite.org/";>SQLite</a>æ¥æ建æå¡å¨å客æ·ç«¯ï¼æ们æ¨è3.6.13ææ´æ°ççæ¬ï¼ä½æ¯3.4.0å·²ç»è¶³å¤ãå¦æå®ä½äºtarballçæ
¹ä¸ï¼Subversionä¼å°è¯ä½¿ç¨SQLite
+<a
href="https://www.sqlite.org/amalgamation.html";>amalgamation</a>ï¼å¦åSubversionä¼å¨ç³»ç»ç常è§ä½ç½®å¯»æ¾SQLiteãä½
ä¹å¯ä»¥éè¿ä¼
éç»<code>configure</code>å½ä»¤<code>--with-sqlite</code>æ¥ææSQLiteåºæamalgamationçä½ç½®ã</p>
</div> <!-- sqlite -->
Modified: subversion/site/publish/docs/release-notes/1.7.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Fri Dec 1 22:34:50 2017
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
@@ -51,7 +51,7 @@ earlier release. The new features will
<p>This page describes only major changes. For a complete list of
changes, see the 1.7 section of the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
file.</p>
</div> <!-- news -->
@@ -98,7 +98,7 @@ cannot necessarily compile or run agains
slightly modified from previous releases. These are cases where edge cases
of the functionality has been deemed buggy, and therefore improved or removed.
Please consult the
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.7/";
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.7/";
>API errata</a> for more detailed information on what these APIs are
and what impact these changes may have. For Subversion 1.7, these
errata are mostly limited to <code>libsvn_wc</code>, with one notable
@@ -367,7 +367,7 @@ the following error:</p>
<pre>
subversion/libsvn_fs_fs/fs_fs.c:1083: (apr_err=160043)
svnadmin: E160043: Found format '5', only created by unreleased dev builds;
- see <a
href="http://subversion.apache.org/docs/release-notes/1.7#revprop-packing";>http://subversion.apache.org/docs/release-notes/1.7#revprop-packing</a>
+ see <a
href="https://subversion.apache.org/docs/release-notes/1.7#revprop-packing";>https://subversion.apache.org/docs/release-notes/1.7#revprop-packing</a>
</pre>
<p>We reiterate that this lack of upgrade path is within the latitude of
@@ -718,7 +718,7 @@ working copy has been added to <code>lib
command-line client to list them all here. Aside from all the ones
mentioned already in these release notes, below are a few more that we
consider important, but please see the 1.7.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for a complete list.</p>
<!-- Insert selected items here -->
@@ -732,7 +732,7 @@ for a complete list.</p>
option which causes it to show changes committed in a revision as
a unified diff. Below is example output:</p>
<pre>
- $ svn log --diff -r1033146 http://svn.apache.org/repos/asf/subversion/trunk
+ $ svn log --diff -r1033146 https://svn.apache.org/repos/asf/subversion/trunk
------------------------------------------------------------------------
r1033146 | hwright | 2010-11-09 19:40:46 +0100 (Tue, 09 Nov 2010) | 3 lines
@@ -858,12 +858,12 @@ files to be shown in their entirety, jus
<strong><tt>--git</tt></strong> option which causes it to produce extra
annotations denoting added, deleted, and copied files.
This extended diff format was inspired by
-<a href="http://www.kernel.org/pub/software/scm/git/docs/git-diff.html";
+<a href="https://www.kernel.org/pub/software/scm/git/docs/git-diff.html";
>git-diff</a>.</p>
<p><tt>svn diff --git</tt> is intended to produce patches which are
compatible to
-<a href="http://www.kernel.org/pub/software/scm/git/docs/git-apply.html";
+<a href="https://www.kernel.org/pub/software/scm/git/docs/git-apply.html";
>git-apply</a>, but there are limitations due to differences between
Subversion and git:
</p>
@@ -935,7 +935,7 @@ what's changed.</p>
<p>As noted <a href="#compatibility">above</a>, a small number of APIs in
<code>libsvn_wc</code> have slightly changed functionality from their
historical roots. Each of these cases has been documented as an
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.7/";>errata</a>,
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.7/";>errata</a>,
detailing the impact of these changes. All of the errata were the result of
behavior which was deemed buggy, and the API changes are an attempt to fix
these bugs. The circumstances under which each is triggered are relatively
@@ -971,7 +971,7 @@ language features.</p>
</h3>
<p>A great many bugs have been fixed. See the 1.7.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
</div> <!-- bug-fixes -->
@@ -1014,7 +1014,7 @@ client-side <tt>servers</tt> configurati
<div class="notice">
<p>Note that
-<a href="http://svn.haxx.se/dev/archive-2011-01/0320.shtml";
+<a href="https://svn.haxx.se/dev/archive-2011-01/0320.shtml";
>server-side configuration changes</a> might be required to avoid
performance regressions for serf clients in some setups.</p>
<p>The <strong>MaxKeepAliveRequests</strong> option in <tt>httpd.conf</tt>
@@ -1030,7 +1030,7 @@ than neon clients it is possible that se
growth of httpd server logs than neon clients do. As of 1.7.3,
the httpd error logs may also grow more rapidly with serf clients
than with neon clients; see
-<a href="http://svn.apache.org/viewvc?rev=1239697&view=rev";
+<a href="https://svn.apache.org/viewvc?rev=1239697&view=rev";
>r1239697</a>.</p>
<p>Known issues with svnrdump that manifest when the latter uses
@@ -1082,7 +1082,7 @@ script given in
<p>While there are scores of bug fixes, performance improvements, and other
changes to merge-tracking, the following are the major changes. See the
1.7.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file for a complete list.</p>
<div class="h4" id="subtree-mergeinfo-recording">
@@ -1355,7 +1355,7 @@ one side of the comparison, the speedup
</h3>
<p>Subversion 1.7 can optionally be compiled with support for
-<a href="http://www.darwinsys.com/file/";>libmagic</a> to detect
+<a href="https://www.darwinsys.com/file/";>libmagic</a> to detect
MIME types of binary files which are added to version control.
This feature is used only for binary files for which no MIME type
is found via auto-props or the mime-types-file configuration option.</p>
@@ -1627,7 +1627,7 @@ Subversion dependencies before building,
<p>Since its inception, Subversion has a used a "modified Apache license".
The migration of the project to the Apache Software Foundation provided
an opprotunity to also change the license to the standard
-<a href="http://www.apache.org/licenses/LICENSE-2.0.html";>Apache License,
+<a href="https://www.apache.org/licenses/LICENSE-2.0.html";>Apache License,
version 2.</a> Additionally, the copyright to the collective work is now
owned by the ASF. While this has very little practical effect, it does mean
consumers have one less license to worry about when deploying Subversion.</p>
@@ -1644,7 +1644,7 @@ consumers have one less license to worry
and <a href="/packages">other release artifacts</a>
are now hosted by the Apache Software Foundation. This includes the official
distribution location, as well as
-<a href="http://archive.apache.org/dist/subversion/";>archives</a> of all
+<a href="https://archive.apache.org/dist/subversion/";>archives</a> of all
previous Subversion releases. Of course, other locations are welcome to
continue to host Subversion distribution artifacts, but the Apache download
sites are now the canonical source for Subversion releases.</p>
@@ -1666,7 +1666,7 @@ hosting platforms. For this reason, and
some of the licenses on these scripts, we have stopped shipping the
<tt>contrib/</tt> directory in the release tarballs. For the time being,
these scripts remain available via the
-<a href="http://svn.apache.org/repos/asf/subversion/trunk/contrib/";>main
+<a href="https://svn.apache.org/repos/asf/subversion/trunk/contrib/";>main
repository</a>.</p>
</div> <!-- contrib -->
Modified: subversion/site/publish/docs/release-notes/1.8.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Fri Dec 1 22:34:50 2017
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
@@ -61,7 +61,7 @@ earlier release. The new features will
<p>This page describes only major changes. For a complete list of
changes, see the 1.8 section of the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
file.</p>
</div> <!-- news -->
@@ -94,7 +94,7 @@ cannot necessarily compile or run agains
slightly modified from previous releases. These are cases where edge cases
of the functionality has been deemed buggy, and therefore improved or removed.
Please consult the
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.8/";
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.8/";
>API errata</a> for more detailed information on what these APIs are
and what impact these changes may have.</p>
@@ -392,7 +392,7 @@ client provider for Subversion.</p>
<div class="notice">
<p>Note that
-<a href="http://svn.haxx.se/dev/archive-2011-01/0320.shtml";
+<a href="https://svn.haxx.se/dev/archive-2011-01/0320.shtml";
>server-side configuration changes</a> might be required to avoid
performance regressions for serf clients in some setups.</p>
<p>The <strong>MaxKeepAliveRequests</strong> option in <tt>httpd.conf</tt>
@@ -428,7 +428,7 @@ repository.</p>
<li>Apache server access log files will grow more quickly due to the larger
number of requests and responses. As of 1.7.3, the httpd error logs may also
grow more rapidly with serf clients than with neon clients; see
-<a href="http://svn.apache.org/viewvc?rev=1239697&view=rev";
+<a href="https://svn.apache.org/viewvc?rev=1239697&view=rev";
>r1239697</a>.</li>
<li>Network traffic can increase drastically when Kerberos or NTLM
authentication is used, as these add a 2 - 4 KB header per HTTP request and
@@ -637,7 +637,7 @@ restricted by mod_authz_svn, but is inst
itself. In order to require authentication on this location, the
location should have "Satisfy All" (which is the default value of this
directive). See examples in mod_authz_svn's <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/mod_authz_svn/INSTALL";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/mod_authz_svn/INSTALL";
>INSTALL</a> document for additional details.</p>
</div> <!-- repos-listing-authz-support -->
@@ -713,7 +713,7 @@ of submodules to do the right thing:
<tt>svn_</tt> or <tt>SVN_</tt>. (Most of these symbols will be
<tt>svn_client_*</tt> symbols, of course.) Star-imports of <tt>from svn</tt>
have
not changed (they import <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/python/svn/core.py";
+href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/python/svn/core.py";
>just the bare submodule names</a>: 'fs', 'ra', etc), and
star imports of <tt>from svn.core</tt> currently imports some select symbols
(notably 'Pool' and 'SubversionException').</p>
@@ -990,34 +990,34 @@ copy. This cache allows the working copy
from the repository without contacting the repository.</p>
<p>For the full details about inheritable properties see the
-<a href="http://wiki.apache.org/subversion/InheritedProperties";
+<a href="https://wiki.apache.org/subversion/InheritedProperties";
>design wiki</a>. Some of this wiki is intended for Subversion developers
and will be of little interest to most users. If you fall into the latter
group you can focus on these particular sections:</p>
<ul>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#Differentiating_.27Inheritable.27_Vs._.27Normal.27_Properties";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#Differentiating_.27Inheritable.27_Vs._.27Normal.27_Properties";>
Differentiating 'Inheritable' Vs. 'Normal' Properties</a>
</li>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#General_Inheritance_Rules";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#General_Inheritance_Rules";>
General Inheritance Rules</a>
</li>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#Repository_Inheritance_Rules";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#Repository_Inheritance_Rules";>
Repository Inheritance Rules</a>
</li>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#Working_Copy_Inheritance_Rules";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#Working_Copy_Inheritance_Rules";>
Working Copy Inheritance Rules</a>
</li>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#Authentication";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#Authentication";>
Authentication</a>
</li>
<li>
- <a
href="http://wiki.apache.org/subversion/InheritedProperties#Subcommand_Changes";>
+ <a
href="https://wiki.apache.org/subversion/InheritedProperties#Subcommand_Changes";>
Subcommand Changes</a>
</li>
</ul>
@@ -1041,10 +1041,10 @@ The <tt>svn:global-ignores</tt> property
<tt>global-ignores</tt> configuration setting as well as the
<tt>svn:ignore</tt> property.</p>
-<p>The <a
href="http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Format";
+<p>The <a
href="https://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Format";
>format</a> of <tt>svn:auto-props</tt> property values
is the same as for the <tt>auto-props</tt> runtime configuration.
-The <a
href="http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Ignores_Format";
+The <a
href="https://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Ignores_Format";
>format</a> of <tt>svn:global-ignores</tt> property values is the
same as for the <tt>svn:ignore</tt> property.</p>
@@ -1076,10 +1076,10 @@ property that applies to the path.</p>
override any identical patterns in the <tt>auto-props</tt> runtime
config. When multiple <tt>svn:auto-props</tt> properties
apply to a file, the pattern from the nearest inheritable property takes
-precedence. See <a
href="http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Hierarchy_and_Precedence";
+precedence. See <a
href="https://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Hierarchy_and_Precedence";
>this section of design wiki</a> for a full explanation.</p>
-<p>The <a
href="http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Hierarchy_and_Precedence";
+<p>The <a
href="https://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Auto-Props_Hierarchy_and_Precedence";
>design wiki</a> for the repository dictated configuration feature was
originally written for developers, but will prove useful to any repository
administrator who wants to use the feature.</p>
@@ -1106,7 +1106,7 @@ will use to ask the user for the passwor
The gpg-agent must be running, and the Subversion client will
need the <tt>GPG_AGENT_INFO</tt> and <tt>GPG_TTY</tt> environment
variables set up correctly.
-See <a
href="http://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html";>this
page</a> for more information about
+See <a
href="https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html";>this
page</a> for more information about
running the gpg-agent.</p>
<p>Cached passwords will persist in memory until the agent process
@@ -1345,7 +1345,7 @@ for <tt>file://</tt> URLs only, not for
such as <tt>http://</tt>, <tt>svn://</tt>, and so on.)</p>
<p>The relative URL syntax should also look familiar, as it mimics
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/cli-repo-root-relative-support.txt";
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/cli-repo-root-relative-support.txt";
>the relative URL syntax</a> that the command-line client recognizes.
When parsing path specifications in this format, Subversion simply
ignores the leading <tt>^/</tt> and looks for authz file at the
@@ -1641,7 +1641,7 @@ See <a href="https://issues.apache.org/j
<div class="notice">
<p>Using general-purpose incremental backup tools, such as
-<a href="http://rsync.samba.org";>rsync</a>, with Subversion repositories
+<a href="https://rsync.samba.org";>rsync</a>, with Subversion repositories
is dangerous if the repository can receive commits while the backup
tool is running. The resulting copy might end up being corrupt because
general-purpose backup tools do not know anything about consistency
@@ -1695,7 +1695,7 @@ $ svnadmin freeze /svn/my-repos -- rsync
<p>The above will obtain a write lock on the <tt>my-repos</tt> repository
to prevent concurrent commits, and run
-<a href="http://rsync.samba.org";>rsync</a> to back up the repository.
+<a href="https://rsync.samba.org";>rsync</a> to back up the repository.
Clients trying to commit concurrently will wait until the write lock
becomes available again. If the command takes too much time clients
trying to commit might time out. It is recommended to run commands
@@ -1796,7 +1796,7 @@ without configuring large fulltext cache
command-line client to list them all here. Aside from all the ones
mentioned already in these release notes, below are a few more that we
consider important, but please see the 1.8.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for a complete list.</p>
<!-- Insert selected items here -->
@@ -1990,7 +1990,7 @@ what's changed.</p>
<p>A small number of APIs have slightly changed functionality from their
historical roots. Each of these cases has been documented as an
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.8/";>errata</a>,
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.8/";>errata</a>,
detailing the impact of these changes. All of the errata were the result of
behavior which was deemed buggy, and the API changes are an attempt to fix
these bugs. The circumstances under which each is triggered are relatively
@@ -2008,7 +2008,7 @@ some may lag more than others.</p>
</h3>
<p>A great many bugs have been fixed. See the 1.8.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file
for details.</p>
</div> <!-- bug-fixes -->
@@ -2023,7 +2023,7 @@ for details.</p>
<p>While there are scores of bug fixes, performance improvements, and other
changes to merge-tracking, the following are the major changes. See the
1.8.0 section in the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file for a complete list.</p>
<div class="h4" id="mergeinfo-r">
@@ -2264,7 +2264,7 @@ do <em>not</em> have names within the re
namespace, of course!) for long-term storage associated with the
commit. An example hook script that renames the revision properties from
<tt>svn:txn-*</tt> to <tt>svn:revision-*</tt> is
-<a
href="http://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/persist-ephemeral-txnprops.py?view=markup";
+<a
href="https://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/persist-ephemeral-txnprops.py?view=markup";
>distributed with Subversion itself</a>.</p>
</div> <!-- ephemeral-txnprops -->
@@ -2301,8 +2301,8 @@ the <a href="https://svn.apache.org/repo
...
</pre>
-<p>svnpubsub was written by <a href="http://people.apache.org/~pquerna/";
-rel="nofollow">Paul Querna</a> for the <a href="http://www.apache.org/dev/";
+<p>svnpubsub was written by <a href="https://people.apache.org/~pquerna/";
+rel="nofollow">Paul Querna</a> for the <a href="https://www.apache.org/dev/";
>ASF Infrastructure Team</a>.</p>
</div> <!-- svnpubsub -->
@@ -2425,7 +2425,7 @@ property set on the file itself will be
</h3>
<p>In the root of every Subversion working copy there is an
-<a href="http://sqlite.org"; >SQLite</a> database in the <tt>.svn</tt>
+<a href="https://sqlite.org"; >SQLite</a> database in the <tt>.svn</tt>
directory and Subversion clients use this database when accessing the
working copy. By default Subversion uses shared SQLite locking and
this allows simultaneous access to the working copy by multiple
@@ -2526,7 +2526,7 @@ to set that option (or to set it to its
you have special circumstances which require it (such as an unusually high
latency), and even then to set it only in the config sections of specific
groups and not in the <tt>[global]</tt> section. See <a
-href="http://mail-archives.apache.org/mod_mbox/subversion-dev/201307.mbox/%3cCADkdwvQUaWaC5=AvwsthjSQWcn48tKHVfWoVCUHjLT=abu1...@mail.gmail.com>">this
dev@ list post</a> for an example.</p>
+href="https://mail-archives.apache.org/mod_mbox/subversion-dev/201307.mbox/%3cCADkdwvQUaWaC5=AvwsthjSQWcn48tKHVfWoVCUHjLT=abu1...@mail.gmail.com>">this
dev@ list post</a> for an example.</p>
</div> <!-- 411-length-required -->
Modified: subversion/site/publish/docs/release-notes/1.9.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Fri Dec 1 22:34:50 2017
@@ -52,7 +52,7 @@ earlier release. The new features will
<p>This page describes only major changes. For a complete list of
changes, see the 1.9 section of the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
+href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES"; >CHANGES</a>
file.</p>
</div> <!-- news -->
@@ -85,7 +85,7 @@ cannot necessarily compile or run agains
slightly modified from previous releases. These are cases where edge cases
of the functionality has been deemed buggy, and therefore improved or removed.
Please consult the
-<a
href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.9/";
+<a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.9/";
>API errata</a> for more detailed information on what these APIs are
and what impact these changes may have.</p>
@@ -410,7 +410,7 @@ the benefits.
their repositories but to eventually migrate them to format 7. For some,
it will be the fast verification feature, others will need the disk I/O
improvements. Note that the key I/O characteristics here is the
-<a href="http://en.wikipedia.org/wiki/Bandwidth-delay_product";>Bandwidth
+<a href="https://en.wikipedia.org/wiki/Bandwidth-delay_product";>Bandwidth
Delay Product</a> of your storage, which is usually between 100kB and 1MB.
Even with SSDs you will see a speed-up, unless your storage bandwidth is
severely limited.
Modified: subversion/site/publish/docs/release-notes/index.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/index.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/index.html (original)
+++ subversion/site/publish/docs/release-notes/index.html Fri Dec 1 22:34:50
2017
@@ -57,7 +57,7 @@ official support status for the various
<p>For a more complete (albeit less descriptive) list of changes made
in individual releases, see
- the <a href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";
+ the <a href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";
>CHANGES</a> file.</p>
<p>For a detailed history of every release, please see
Modified: subversion/site/publish/docs/release-notes/release-history.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/release-history.html?rev=1816924&r1=1816923&r2=1816924&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/release-history.html (original)
+++ subversion/site/publish/docs/release-notes/release-history.html Fri Dec 1
22:34:50 2017
@@ -24,7 +24,7 @@
<p>Pre-1.0 releases that included a change in the filesystem database
schema (and therefore required a repository <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO";
+href="https://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO";
>reload</a>), are highlighted in <span style="color: red"
><b><i>red</i></b></span>. There will be no more such releases before
Subversion 2.0.</p>
@@ -347,8 +347,8 @@ Subversion 2.0.</p>
<li>
<b>Beta (1.0-stabilization):</b> Branched from 0.35.0,
see <a
-
href="http://svn.apache.org/repos/asf/subversion/branches/1.0-stabilization/";
-
>http://svn.apache.org/repos/asf/subversion/branches/1.0-stabilization/</a>.
+
href="https://svn.apache.org/repos/asf/subversion/branches/1.0-stabilization/";
+
>https://svn.apache.org/repos/asf/subversion/branches/1.0-stabilization/</a>.
</li>
<li>
<b>Subversion 0.35</b> (19 December 2003):
@@ -499,8 +499,8 @@ Subversion 2.0.</p>
interim releases, will increment the minor (middle) number;
and the patch (rightmost) number will indicate the iteration
of the release, for cases where we do post-release bugfixing.
- See <a href="http://apr.apache.org/versioning.html";
- >http://apr.apache.org/versioning.html</a> for more details.
+ See <a href="https://apr.apache.org/versioning.html";
+ >https://apr.apache.org/versioning.html</a> for more details.
</li>
<li>
<b>Subversion 0.14.4</b> (29 October 2002): Interim
@@ -636,7 +636,7 @@ Subversion 2.0.</p>
href="https://issues.apache.org/jira/browse/SVN-608";>issue
#608</a>); and many small features and bugfixes since 0.8, all
praise to the Conquering Developer Hordes. See the
- <a
href="http://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
+ <a
href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES";>CHANGES</a>
file for details.
</li>
<li> <b>Subversion 0.8</b> (14 January 2002): Commit system rewrite (<a
