You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ds...@apache.org on 2021/07/08 21:54:05 UTC
svn commit: r1891386 [1/2] - in /subversion/site/publish: ./ docs/
docs/community-guide/ docs/release-notes/
Author: dsahlberg
Date: Thu Jul 8 21:54:05 2021
New Revision: 1891386
URL: http://svn.apache.org/viewvc?rev=1891386&view=rev
Log:
In site/publish:
Merge r1891385 from staging
Modified:
subversion/site/publish/ (props changed)
subversion/site/publish/docs/community-guide/general.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.11.html
subversion/site/publish/docs/release-notes/1.12.html
subversion/site/publish/docs/release-notes/1.13.html
subversion/site/publish/docs/release-notes/1.14.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/faq.html
subversion/site/publish/faq.ja.html
subversion/site/publish/faq.zh.html
subversion/site/publish/ideas.html
subversion/site/publish/index.html (props changed)
subversion/site/publish/mailing-lists.html
subversion/site/publish/news.html (props changed)
subversion/site/publish/quick-start.html
subversion/site/publish/roadmap.html (props changed)
subversion/site/publish/site-nav.html
Propchange: subversion/site/publish/
------------------------------------------------------------------------------
Merged /subversion/site/staging:r1891286-1891385
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Thu Jul 8 21:54:05 2021
@@ -160,8 +160,8 @@ href="https://svn.apache.org/repos/asf/s
O'Reilly that shows in detail how to effectively use Subversion.
The text of the book is free, and is actively being revised.
On-line versions are available
- at <a href="http://svnbook.red-bean.com/"
- >http://svnbook.red-bean.com/</a>. The XML source and
+ at <a href="https://svnbook.red-bean.com/"
+ >https://svnbook.red-bean.com/</a>. The XML source and
translations to other languages are maintained in their own
repository at <a href="https://sourceforge.net/projects/svnbook/"
>https://sourceforge.net/projects/svnbook/</a>.</p>
Modified: subversion/site/publish/docs/index.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/index.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/index.html (original)
+++ subversion/site/publish/docs/index.html Thu Jul 8 21:54:05 2021
@@ -39,8 +39,8 @@
Subversion</span> (affectionately known as "the Subversion book")
— carries a free license, was developed openly by the
Subversion community itself, and is also available in full online
- for free at <a href="http://svnbook.red-bean.com/"
- >http://svnbook.red-bean.com</a>.</p>
+ for free at <a href="https://svnbook.red-bean.com/"
+ >https://svnbook.red-bean.com</a>.</p>
</div> <!-- #user-manuals -->
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.1.html (original)
+++ subversion/site/publish/docs/release-notes/1.1.html Thu Jul 8 21:54:05 2021
@@ -19,11 +19,11 @@
<h1 style="text-align: center">Subversion 1.1 Release Notes</h1>
<h2 style="text-align: center">(and State of the Project)</h2>
-<p>The <a href="http://svnbook.red-bean.com/">Subversion book site</a>
+<p>The <a href="https://svnbook.red-bean.com/">Subversion book site</a>
has now been forked, and a separate <a
-href="http://svnbook.red-bean.com/svnbook-1.1/index.html">Subversion
+href="https://svnbook.red-bean.com/svnbook-1.1/index.html">Subversion
1.1 book</a> documents most of <a
-href="http://svnbook.red-bean.com/svnbook-1.1/pr02s07.html">the new
+href="https://svnbook.red-bean.com/svnbook-1.1/pr02s07.html">the new
1.1 features</a>. Still, here are some brief release notes.</p>
<div class="h3" id="overview">
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.10.html (original)
+++ subversion/site/publish/docs/release-notes/1.10.html Thu Jul 8 21:54:05 2021
@@ -54,7 +54,7 @@ releases, and is as of the time of its r
in 1.10, but 1.10 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.10 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.10 section of the <a
@@ -75,7 +75,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.10 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
@@ -734,7 +734,7 @@ file.</p>
<p>In order to speed up read and write operations for existing repositories,
consider recompressing the data stored in them with LZ4. This can be achieved
by performing a full
-<a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">dump/load</a>
+<a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">dump/load</a>
cycle into a new format 8 repository created with Subversion 1.10.
</div> <!-- fsfs-lz4-configuration -->
@@ -1029,7 +1029,7 @@ thus ensuring that the appropriate value
other changes made to the repository. This is useful because revision
properties are not versioned but their values may change if the administrator
has configured the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.ref.reposhooks.pre-revprop-change.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.ref.reposhooks.pre-revprop-change.html"
>repository's pre-revprop-change hook</a>.</p>
<p><tt>svnadmin dump-revprops</tt> will save the current values of all revision
Modified: subversion/site/publish/docs/release-notes/1.11.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.11.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.11.html (original)
+++ subversion/site/publish/docs/release-notes/1.11.html Thu Jul 8 21:54:05 2021
@@ -61,7 +61,7 @@ releases, and is as of the time of its r
in 1.11, but 1.11 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.11 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.11 section of the <a
@@ -82,7 +82,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.11 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
Modified: subversion/site/publish/docs/release-notes/1.12.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.12.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.12.html (original)
+++ subversion/site/publish/docs/release-notes/1.12.html Thu Jul 8 21:54:05 2021
@@ -58,7 +58,7 @@ releases, and is as of the time of its r
in 1.12, but 1.12 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.12 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.12 section of the <a
@@ -79,7 +79,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.12 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
Modified: subversion/site/publish/docs/release-notes/1.13.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.13.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.13.html (original)
+++ subversion/site/publish/docs/release-notes/1.13.html Thu Jul 8 21:54:05 2021
@@ -50,7 +50,7 @@ releases, and is as of the time of its r
in 1.13, but 1.13 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.13 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.13 section of the <a
@@ -71,7 +71,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.13 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
Modified: subversion/site/publish/docs/release-notes/1.14.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.14.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.14.html (original)
+++ subversion/site/publish/docs/release-notes/1.14.html Thu Jul 8 21:54:05 2021
@@ -81,7 +81,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.14 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.2.html (original)
+++ subversion/site/publish/docs/release-notes/1.2.html Thu Jul 8 21:54:05 2021
@@ -38,7 +38,7 @@ Anything in 1.0.x and 1.1.x is also in 1
and bugfixes not present in any earlier release. The new features
will eventually be documented in a 1.2 version of the free Subversion
book, see
-<a href="http://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
+<a href="https://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
</div>
@@ -187,7 +187,7 @@ use Berkeley DB 4.3. Please be warned!<
<p>"Locking" is a long-requested feature, often known in other systems
as "reserved checkouts". While Subversion is still primarily a <a
-href="http://svnbook.red-bean.com/en/1.1/ch02s02.html#svn-ch-2-sect-2.3">copy-modify-merge</a>
+href="https://svnbook.red-bean.com/en/1.1/ch02s02.html#svn-ch-2-sect-2.3">copy-modify-merge</a>
system focused on parallel development, there is widespread
acknowledgement that not all files are easily mergeable —
binary files in particular, such as artwork, compressed files,
@@ -201,7 +201,7 @@ unmergable changes.</p>
<p>This feature is now documented in the nightly build of the svn 1.2
book,
available <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html">here</a>.
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html">here</a>.
(Note that this link is temporary; when the 1.2 book is finished, the
URL may change.)</p>
@@ -233,7 +233,7 @@ can still use Subversion clients to exam
<p>Prior to Subversion 1.2, mod_dav_svn had only partial
interoperability with generic DAV clients. <a
-href="http://svnbook.red-bean.com/en/1.1/apc.html">Appendix C</a> in
+href="https://svnbook.red-bean.com/en/1.1/apc.html">Appendix C</a> in
the Subversion 1.1 book documented the trials and tribulations of this
exercise. At most, one could use a DAV client to drag files into a
mounted repository, but the files couldn't be edited directly from the
@@ -263,7 +263,7 @@ vary.</p>
<p>This feature is now documented in the nightly build of the svn 1.2
book,
available <a
-href="http://svnbook.red-bean.com/nightly/en/svn.webdav.html">here</a>.
+href="https://svnbook.red-bean.com/nightly/en/svn.webdav.html">here</a>.
(Note that this link is temporary; when the 1.2 book is finished, the
URL may change.)</p>
@@ -373,7 +373,7 @@ currently underway (with Sleepycat engin
Berkeley DB repositories are still older and better-tested than FSFS
repositories in terms of scalability; the project still recommends you
<a
-href="http://svnbook.red-bean.com/en/1.1/ch05.html#svn-ch-5-sect-1.3">read
+href="https://svnbook.red-bean.com/en/1.1/ch05.html#svn-ch-5-sect-1.3">read
about the two back-ends in the book</a> and make an informed
choice.</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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.3.html (original)
+++ subversion/site/publish/docs/release-notes/1.3.html Thu Jul 8 21:54:05 2021
@@ -41,7 +41,7 @@ Anything in 1.0.x, 1.1.x, or 1.2.x is al
features and bugfixes not present in any earlier release. The new
features will eventually be documented in a 1.3 version of the free
Subversion book, see
-<a href="http://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
+<a href="https://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
</div> <!-- news -->
@@ -177,7 +177,7 @@ pre-commit hook scripts.)</p>
<p>The authorization file format is the same
one <a
-href="http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.2"
+href="https://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.2"
>described here</a>, in Chapter 6 of the Subversion book. You simply
need to point to it from your repository's <em>svnserve.conf</em>
file using the new <tt>authz-db</tt> directive:</p>
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.4.html (original)
+++ subversion/site/publish/docs/release-notes/1.4.html Thu Jul 8 21:54:05 2021
@@ -42,7 +42,7 @@ release. Anything in 1.0.x, 1.1.x, 1.2.
1.4 contains features and bugfixes not present in any earlier release.
The new features will eventually be documented in a 1.4 version of the
free Subversion book,
-see <a href="http://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
+see <a href="https://svnbook.red-bean.com/">svnbook.red-bean.com</a>.</p>
</div> <!-- news -->
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.5.html (original)
+++ subversion/site/publish/docs/release-notes/1.5.html Thu Jul 8 21:54:05 2021
@@ -61,7 +61,7 @@ release. Any feature or bugfix in 1.0.x
but 1.5 contains features and bugfixes not present in any earlier
release. The new features will eventually be documented in a 1.5
version of the free Subversion book,
-see <a href="http://svnbook.red-bean.com/"
+see <a href="https://svnbook.red-bean.com/"
>svnbook.red-bean.com</a>.</p>
</div> <!-- news -->
@@ -365,7 +365,7 @@ afterwards. In the meantime:</p>
<li><p>Take a look at <a href="#mt-known-issues"
>the list of known issues</a></p></li>
<li><p>Read <a
- href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.finalword"
+ href="https://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="https://www.collab.net/community/subversion/articles/merge-info.html"
@@ -438,7 +438,7 @@ versions trivially differ, you can just
merged. (See <a
href="https://svn.apache.org/repos/asf/subversion/trunk/notes/merge-tracking/requirements.html#manual-merge"
>the merge-tracking requirements</a>, and <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.blockchanges"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.blockchanges"
>Blocking Changes</a> in the Subversion book, for more details.)</p>
</div> <!-- mt-record-only -->
@@ -446,14 +446,14 @@ href="http://svnbook.red-bean.com/nightl
<p>The --reintegrate option is used when merging a branch back to
trunk; it checks for some common safeguard conditions and then does
the merge in a fast and efficient way. See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.stayinsync"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.stayinsync"
>Keeping a branch in sync</a> in the Subversion book for more.</p>
</div> <!-- mt-reintegrate -->
<p>The new <strong><code>svn mergeinfo</code></strong> command can
show which changesets a directory has absorbed and which changesets
it's still eligible to receive. See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.mergeinfo"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.mergeinfo"
>Mergeinfo and Previews</a> in the Subversion book for more information.</p>
<p>The <strong><code>svn log</code></strong> and
@@ -473,7 +473,7 @@ output, the original changes that were l
revisions; again, -g includes the latter information (tagged with
lines that say "<tt>Merged via: </tt>" followed by the revision number
in which the merge took place). See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.logblame"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.logblame"
>Merge-Sensitive Logs and Annotations</a> in the Subversion book for
more details.</p>
@@ -597,7 +597,7 @@ then this problem won't happen in the fi
<p>For more on merge-tracking in Subversion 1.5, see:</p>
<ul>
-<li><a href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html"
+<li><a href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.html"
>Chapter 4: Branching and Merging</a> in the Subversion book
</li>
<li><a href="http://blog.red-bean.com/sussman/?p=92" >Subversion 1.5
@@ -755,7 +755,7 @@ this alleviates some of the extra networ
<ul>
<li>The <a
- href="http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html"
+ href="https://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html"
>Sparse Directories</a> section in the Subversion book.
</li>
<li>The <a
@@ -881,7 +881,7 @@ subcommands:</p>
<ul>
<li>The <a
- href="http://svnbook.red-bean.com/nightly/en/svn.advanced.changelists.html"
+ href="https://svnbook.red-bean.com/nightly/en/svn.advanced.changelists.html"
>Changelists</a> section in the Subversion book.
</li>
<li>The <a
@@ -1052,7 +1052,7 @@ the target directory.</p>
</h4>
<p>See The <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
>svn:externals</a> section of the Subversion Book.</p>
</div> <!-- externals-further-reading -->
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.6.html (original)
+++ subversion/site/publish/docs/release-notes/1.6.html Thu Jul 8 21:54:05 2021
@@ -61,7 +61,7 @@ releases, and is as of the time of its r
in 1.6, but 1.6 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.6 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.6 section of the <a
@@ -485,7 +485,7 @@ external.</p>
</h4>
<p>See The <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
>svn:externals</a> section of the Subversion Book.</p>
</div> <!-- further-reading -->
@@ -526,7 +526,7 @@ no changes.</p>
</h4>
<p>See the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html"
>tree conflicts</a> section of the Subversion Book.</p>
</div> <!-- tree-conflicts-further-reading -->
@@ -786,7 +786,7 @@ to work directly against repositories wi
<p>As with the commandline, the peg revision defaults to HEAD if
unspecified, and the operative revision defaults to the peg
revision. The online Subversion Book has
- a <a href="http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html">section
+ a <a href="https://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html">section
explaining peg and operative revisions</a> in great detail.</p>
</div> <!-- historical-uris -->
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.6.zh.html (original)
+++ subversion/site/publish/docs/release-notes/1.6.zh.html Thu Jul 8 21:54:05 2021
@@ -55,7 +55,7 @@
>è¶
è¿65项æ°çbugä¿®æ£åæå</a></li>
</ul>
-<p>Subversion 1.6æ¯ææ以åSubversionçæ¬çè¶
éï¼å¯ä»¥è®¤ä¸ºæ¯å½åæ好ççæ¬ãä»»ä½1.0.xå°1.5.xçbugä¿®æ£åç¹æ§ï¼é½åå¨äº1.6ä¸ãæ°çç¹æ§æç»ä¼çºªå½å¨Subversionå¾ä¹¦ä¸(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>)ã
+<p>Subversion 1.6æ¯ææ以åSubversionçæ¬çè¶
éï¼å¯ä»¥è®¤ä¸ºæ¯å½åæ好ççæ¬ãä»»ä½1.0.xå°1.5.xçbugä¿®æ£åç¹æ§ï¼é½åå¨äº1.6ä¸ãæ°çç¹æ§æç»ä¼çºªå½å¨Subversionå¾ä¹¦ä¸(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>)ã
</p>
<p>æ¬ææè¿°äºä¸»è¦çåæ´ï¼å®æ´çå表å¯ä»¥ç<a
@@ -379,7 +379,7 @@ Keyring, Mac OS Keychain以åWind
</h4>
<p>å¯ä»¥çSubversionå¾ä¹¦ç<a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
>svn:externals</a>å°èã</p>
</div> <!-- further-reading -->
@@ -408,7 +408,7 @@ href="http://svnbook.red-bean.com/nightl
</h4>
<p>Subversionå¾ä¹¦ç<a
-href="http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html"
>tree conflicts</a>å°èã</p>
</div> <!-- tree-conflicts-further-reading -->
@@ -602,7 +602,7 @@ update</code>ç<code>--set-depth</co
<pre>http://host/repos/path?p=38&r=20</pre>
-<p>åå½ä»¤è¡ä¸æ ·ï¼peg修订çæ¬ç¼ºçä¸HEADç¸åï¼èæä½ä¿®è®¢çæ¬åé»è®¤ä¸peg修订çæ¬ç¸åãå¨çº¿å¾ä¹¦<a href="http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html">è¿ä¸ªå°è</a>详ç»ä»ç»äºè¿äºä¸è¥¿ã</p>
+<p>åå½ä»¤è¡ä¸æ ·ï¼peg修订çæ¬ç¼ºçä¸HEADç¸åï¼èæä½ä¿®è®¢çæ¬åé»è®¤ä¸peg修订çæ¬ç¸åãå¨çº¿å¾ä¹¦<a href="https://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html">è¿ä¸ªå°è</a>详ç»ä»ç»äºè¿äºä¸è¥¿ã</p>
</div> <!-- historical-uris -->
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Thu Jul 8 21:54:05 2021
@@ -47,7 +47,7 @@ releases, and is as of the time of its r
in 1.7, but 1.7 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.7 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.7 section of the <a
@@ -640,7 +640,7 @@ from the network access library than
with the <a href="#serf">ra_serf HTTP access library</a>, as documented
in <a href="https://issues.apache.org/jira/browse/SVN-4116"
>issue #4116</a>. A workaround is to
-<a href="http://svnbook.red-bean.com/en/1.7/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers"
+<a href="https://svnbook.red-bean.com/en/1.7/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers"
>use the ra_neon HTTP access library</a> (which is the default).</p>
<p>The problem does not affect other executables (such as <tt>svn</tt> and
@@ -1158,7 +1158,7 @@ changes resulting from this merge.</p>
<p>To prevent unnecessary conflicts, <tt>svn merge</tt> will now fail
with an error if the merge target is a
-<a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
+<a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
>mixed-revision working copy</a>.</p>
<p>A mixed-revision working copy will need to be updated with
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Thu Jul 8 21:54:05 2021
@@ -57,7 +57,7 @@ releases, and is as of the time of its r
in 1.8, but 1.8 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.8 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.8 section of the <a
@@ -78,7 +78,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.8 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
@@ -155,7 +155,7 @@ and what impact these changes may have.<
<td>1.8</td>
<td>1.8</td>
<td><a href="#fsfs-deltification">Repository size reduction</a>
- requires <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+ requires <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump/load</a>.</td></tr>
<tr>
<td><a href="#in-repo-authz">Authz file in repository</a></td>
@@ -661,7 +661,7 @@ only as of 1.8.0 does 'svnadmin verify'
detect instances of that corruption in the history of a repository.</p>
<p>The fix to these issues is simple: perform a <a
-href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump/load cycle</a>. (As usual, svnsync can be used instead of dump/load.)
The cycle can be done with any version of Subversion, and after the cycle the
repository should be served exclusively by Subversion 1.7.5 or newer to prevent
@@ -794,7 +794,7 @@ These links are shown by <tt>svn status<
specially. Behavioural changes include:</p>
<ul>
<li><p><tt>svn move</tt> now refuses to move a
- <a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
+ <a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
>mixed-revision working copy</a>.</p></li>
<li><p><tt>svn commit</tt> will only commit a moved file or directory
if both sides of the move are part of the same commit. This ensures
@@ -838,7 +838,7 @@ specially. Behavioural changes include:<
<p>During merges which merge all eligible revisions from another
branch, Subversion 1.8 will automatically decide whether or not
the merge is <a
-href="http://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate"
+href="https://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate"
>reintegrating a branch</a>.
Therefore, reintegrating a branch does no longer require the
<tt>--reintegrate</tt> option for correct operation.</p>
@@ -854,10 +854,10 @@ in its top-level directory:</p>
<tt>svn merge --reintegrate</tt> performed in earlier releases:
<ul>
<li>The working copy must not be a <a
-href="http://svnbook.red-bean.com/en/1.7/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
+href="https://svnbook.red-bean.com/en/1.7/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
>mixed-revision working copy</a>.</li>
<li>The working copy must not have <a
-href="http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html"
+href="https://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html"
>switched subtrees</a>.</li>
<li>There must be no gaps in revision ranges merged from the reintegration
target (e.g. the trunk) to the reintegration source (i.e. the branch to be
@@ -872,7 +872,7 @@ merge into a working copy with local mod
<p>Merging to-and-fro between two branches in any order is possible
using the automatic reintegration merge (the "<a
-href="http://svnbook.red-bean.com/en/1.7/svn.branchmerge.advanced.html#svn.branchmerge.advanced.reintegratetwice"
+href="https://svnbook.red-bean.com/en/1.7/svn.branchmerge.advanced.html#svn.branchmerge.advanced.reintegratetwice"
>keep-alive dance</a>" is no longer necessary).
For best results, it is recommended to
@@ -1036,7 +1036,7 @@ group you can focus on these particular
and <tt>svn:global-ignores</tt> make use of the new
<a href="#iprops">inherited properties</a> feature to provide additional
configuration information that overrides/extends some of the settings
-found in the user's <a href="http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.confarea.opts.config"
+found in the user's <a href="https://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.confarea.opts.config"
>runtime configuration</a>. The <tt>svn:auto-props</tt>
property overrides/extends the <tt>auto-props</tt> configuration setting.
The <tt>svn:global-ignores</tt> property extends the
@@ -1163,7 +1163,7 @@ the <tt>--compatible-version 1.6</tt> pa
<p>You may use <tt>svnadmin upgrade</tt> to upgrade existing repositories.
However, to fully benefit from the latest <a href="#fsfs-deltification">repository size reductions</a>,
it is recommended to create a new repository, adjust its settings and then
-<a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump/load</a> or svnsync the contents into it.
</p>
@@ -1279,7 +1279,7 @@ and properties. Hence, Subversion 1.6 an
them but will always write new revisions without that optimization.
It is therefore perfectly legal to create a pre-1.8-compatible
repository in 1.8, to enable various deltification options, to <a
-href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump/load</a> into that new repository using 1.8 tooling and to
finally use the repository with a 1.6 or 1.7 server.
</p>
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=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Thu Jul 8 21:54:05 2021
@@ -48,7 +48,7 @@ releases, and is as of the time of its r
in 1.9, but 1.9 contains features and bugfixes not present in any
earlier release. The new features will eventually be documented in a
1.9 version of the free Subversion book
-(<a href="http://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
+(<a href="https://svnbook.red-bean.com/" >svnbook.red-bean.com</a>).</p>
<p>This page describes only major changes. For a complete list of
changes, see the 1.9 section of the <a
@@ -69,7 +69,7 @@ available unless both client and server
also cases where a new feature will work but will run less efficiently if
the client is new and the server old.</p>
-<p>There is <strong>no need</strong> to <a href="http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
+<p>There is <strong>no need</strong> to <a href="https://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin"
>dump and reload</a> your repositories.
Subversion 1.9 servers can read and write to repositories created by
earlier versions. To upgrade an existing server installation, just install the
@@ -292,7 +292,7 @@ your repository. However, the new addre
will not be used in that case but only in repositories that got created as format
7. For best performance and to enable all features, it is recommended to
perform a full
-<a href="http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">
+<a href="https://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">
dump / load</a> cycle. You can tell whether all format 7 features are enabled
by looking for <tt>FSFS Logical Addressing: yes</tt> in the output of
<tt>svnadmin info</tt>: if that line is printed, then the repository has
@@ -729,7 +729,7 @@ respect to the feature set that its deve
it keeps its experimental status, there will be neither forward nor backward
compatibility between FSX repositories of different Subversion feature releases.
Subversion 1.10 and later will recognize 1.9 FSX repositories and error out
-on them. You may use <a href="http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">
+on them. You may use <a href="https://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin">
dump and load</a> to upgrade an FSX repository from one release to another.</p>
<p>Dump and load is also the only upgrade path between FSFS and FSX.</p>
@@ -1247,7 +1247,7 @@ by the interactive conflicts resolver in
<p>The old, two-way conflict markers output can be obtained by setting
<tt>diff3-cmd</tt> in the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html"
>Subversion runtime configuration</a> (or via the <tt>--config-option</tt>
or <tt>--diff3-cmd</tt> command-line options) to a <tt>diff3</tt>
command that generates two-way conflict markers. Your system may already
@@ -1278,7 +1278,7 @@ will be.</p>
next revision that changed (or removed) that line would be, run
<tt>svn blame -r HEAD:3 README.txt</tt>. (You may need to pass a
<!-- TODO: link points to nightly (no 1.9 book branch yet) -->
-<a href="http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html">peg
+<a href="https://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html">peg
revision</a> if the file had been renamed since r3.)</p>
<p>In the <tt>blame</tt> command, the range <tt>-r M:N</tt> always means
Modified: subversion/site/publish/faq.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/faq.html (original)
+++ subversion/site/publish/faq.html Thu Jul 8 21:54:05 2021
@@ -482,7 +482,7 @@ use Subversion?
<p>For more details about setting up a network accessible Subversion
server, see <a
-href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.html"
>chapter 6</a> in the Subversion book.</p>
</div>
@@ -541,9 +541,9 @@ projects, but Subversion doesn't treat t
sub-tree. Thus, the interpretation of what constitutes a project in
the repository is left entirely up to the users. (This is similar to
how <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html"
>branches</a> and <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html"
>tags</a> are conventions built on top of copies, instead of being
basic concepts built into Subversion itself.)</p>
@@ -567,7 +567,7 @@ number. Also, the revision number shoul
publicly-visible release number of a particular project in the
repository. For that, you should devise some other mechanism of
distinguishing releases, such as using <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html"
>tags</a>.</p>
</div>
@@ -701,7 +701,7 @@ and in
<p>If you don't find an answer after browsing this FAQ, there are several
other resources available:</p>
<ul>
- <li><a href="http://svnbook.red-bean.com/">The Subversion <b>Book</b></a>
+ <li><a href="https://svnbook.red-bean.com/">The Subversion <b>Book</b></a>
(free to read online)</li>
<li>The Subversion Users <b>mailing list</b>
<a href="mailto:users@subversion.apache.org">users@subversion.apache.org</a>
@@ -843,11 +843,11 @@ import data into it?
<p>See <a
href="/quick-start">Quick Start</a>. For some more detail, see the
-<a href="http://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html">
+<a href="https://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html">
quick start instructions in The Subversion Book</a>.</p>
<p>For even more detail about repository setup and administration, read
-<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html">
+<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.html">
chapter 5 in The Subversion Book</a>.</p>
</div>
@@ -943,7 +943,7 @@ running <tt>svn --version</tt>.</p>
<p>A simple option is to use the <b>svnserve</b> server instead of
Apache. See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.html"
>chapter 6</a> in the Subversion book for details.</p>
<p>However, if your admins don't want you to run Apache, it's very
@@ -1175,7 +1175,7 @@ owns the repository.</p>
<p>If your clients are accessing via <tt>file:///</tt> or
<tt>svn+ssh://</tt>, then there's no way to avoid access by multiple
users. In that case, read <a
-href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html"
>the last section in chapter 6</a>, and pay particular attention to the
"checklist" sidebar at the bottom. It outlines a number of steps to
make this scenario safer.</p>
@@ -1231,12 +1231,12 @@ href="https://issues.apache.org/jira/bro
<p>In the meantime, your only recourse is to <b>svnadmin dump</b> your
repository, then pipe the dumpfile through <b>svndumpfilter</b>
(excluding the bad path) into an <b>svnadmin load</b> command. See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.html"
>chapter 5</a> of the Subversion book for details about this.</p>
-<p>An alternative approach is to <a href="http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.replication"
+<p>An alternative approach is to <a href="https://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.replication"
>replicate the repository with <b>svnsync</b></a> after configuring
-<a href="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html"
+<a href="https://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html"
>path-based authorization</a>
rules that deny read access to any paths that need to be filtered from
history. Unlike <b>svndumpfilter</b>, <b>svnsync</b> will automatically
@@ -1258,7 +1258,7 @@ How do I change the log message for a re
<p>Log messages are kept in the repository as properties attached to each
revision. By default, the log message property (<em>svn:log</em>) cannot be
edited once it is committed. That is because changes to <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html">revision
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html">revision
properties</a> (of which <em>svn:log</em> is one) cause the property's
previous value to be permanently discarded, and Subversion tries to prevent
you from doing this accidentally. However, there are a couple of ways to get
@@ -1267,7 +1267,7 @@ Subversion to change a revision property
<p>The first way is for the repository administrator to enable revision
property modifications. This is done by creating a hook called
"pre-revprop-change" (see <a
-href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks"
+href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks"
>this section</a> in the Subversion book for more details about how to do
this). The "pre-revprop-change" hook has access to the old log message
before it is changed, so it can preserve it in some way (for example, by
@@ -1406,7 +1406,7 @@ it. If you don't see such a notice, the
change, and no dump/load is necessary.</p>
<p>An alternative to dump/load is using
-<a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.replication"
+<a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.replication"
>svnsync</a> to replicate the repository into a new one. This is a bit
slower, but is more flexible, and has some extra normalization-features
which are not (yet) available with dump/load (svnsync normalizes properties
@@ -1419,7 +1419,7 @@ database, not the repository hook script
locks</b>. These need to be copied over manually from source to target
(see below in the "complex procedure").
If you need to copy the complete repository, without rebuilding the back-end
-database, <a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.backup"
+database, <a href="https://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.backup"
>svnadmin hotcopy</a> may be a better option.</p>
<p>For small repositories that can afford some downtime, this is a
@@ -1620,7 +1620,7 @@ and then continue with a new "piped" com
</ul>
<p> See
-<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate"
+<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate"
>this section of the Subversion book</a> for more details on dumping and
loading.</p>
@@ -2173,7 +2173,7 @@ mechanism to automatically set propertie
This means that all of your users need to remember to set certain
properties whenever they <tt>svn add</tt> a file. Fortunately,
there's a client-side tool to help with this. Read about the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto"
>auto-props</a> feature in the book. You need to make sure all your
users configure their clients' auto-props settings appropriately.</p>
@@ -2273,7 +2273,7 @@ every commit?
<p>This is done all the time, and is easily accomplished by adding a
post-commit hook script to your repository. Read about hook scripts
in <a
-href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks"
+href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks"
>Chapter 5</a> of the book. The basic idea is to make the "live site"
just an ordinary working copy, and then have your post-commit hook
script run 'svn update' on it.</p>
@@ -2473,7 +2473,7 @@ Subversion calls the file binary.</p>
<p>If Subversion determines that the file is binary, the file receives
an svn:mime-type property set to "application/octet-stream". (You can
always override this by using the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto"
+href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto"
>auto-props feature</a> or by setting the property manually with
<tt>svn propset</tt>.)</p>
@@ -2636,7 +2636,7 @@ divergent branch, while still incorporat
upstream source. This is commonly called a <em>vendor branch</em>
(the term long predates Subversion), and the techniques for
maintaining one in Subversion are <a
-href="http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.advanced.vendorbr"
+href="https://svnbook.red-bean.com/en/1.4/svn-book.html#svn.advanced.vendorbr"
>described here</a>.</p>
<p>If the vendor code is hosted in a remote Subversion repository,
@@ -2662,7 +2662,7 @@ identical files.</p>
</h3>
<p>Use 'svn merge' or 'svn copy', as <a
-href="http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.undo"
+href="https://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.undo"
>described in the Subversion book</a>.</p>
</div>
@@ -2742,9 +2742,9 @@ working copy is out of date?
(for example, directory property modifications), if the
repository has a more recent version of the node, the commit will
be rejected, to prevent data loss. See <a
- href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.limits"
+ href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.limits"
>Mixed revisions have limitations</a> in the <a
- href="http://svnbook.red-bean.com/">Version Control with
+ href="https://svnbook.red-bean.com/">Version Control with
Subversion</a> book for details.</p>
<p>You can fix the problem by running 'svn update' in the working
@@ -2880,7 +2880,7 @@ a <tt>file:</tt> URL?
svn import file:///d:/some/path/to/repos/on/d/drive
</pre>
<p>See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.advanced.reposurls">
+href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.advanced.reposurls">
Subversion Repository URLs</a> in the Subversion Book for more
details.</p>
@@ -3008,7 +3008,7 @@ rev 24: (no author) | 2003-07-29 1
</pre></blockquote>
<p>See <a
-href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html"
+href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html"
>the Subversion book</a>
to learn about configuring access restrictions in Apache.</p>
@@ -3333,8 +3333,8 @@ may find the script here:</p>
<h4>Additional Information</h4>
<p>More information on password caching is in Chapter 6 of the <a
-href="http://svnbook.red-bean.com/en/1.7/index.html">Subversion book</a>,
-under <a href="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache"
+href="https://svnbook.red-bean.com/en/1.7/index.html">Subversion book</a>,
+under <a href="https://svnbook.red-bean.com/en/1.7/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache"
>"Client Credentials Caching".</a></p>
</div>
@@ -3379,7 +3379,7 @@ new HEAD revision might be r20.</li>
</ul>
<p>You now have what is known as a
-<i><a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.update-commit">mixed revision working copy</a></i>.
+<i><a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.update-commit">mixed revision working copy</a></i>.
One file is at r20, but all other files remain at r7 until they too are
committed, or until '<tt>svn update</tt>' is run.</p>
@@ -3981,7 +3981,7 @@ The other files/directories (possibly in
from!) don't get their base revisions bumped, which means Subversion still
considers them to be based on outdated revisions.
See also <a href="#hidden-log">this question</a> and
-<a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.update-commit">this
+<a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.update-commit">this
section of the Subversion book</a>.
</p>
@@ -4105,7 +4105,7 @@ the following rules can be kept in mind:
<li>When copying/renaming a file or directory <em>within</em> the trunk
or a branch, perform the copy/rename in a working copy. For renames,
the working copy should <em>not</em> be a <a
- href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
+ href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs"
>mixed-revision working copy</a>.</li>
<li>When copying/renaming an entire branch, perform the copy/rename in
the repository (i.e. via URLs).</li>
@@ -4155,10 +4155,10 @@ server systems. See <a href="https://mai
single-sign-on mechanism, such as Kerberos or SSPI.
See the <a href="https://httpd.apache.org/docs/"
>Apache HTTPD server documentation</a> for details.
-If you are using svnserve, see the <a href="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl"
+If you are using svnserve, see the <a href="https://svnbook.red-bean.com/en/1.7/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl"
>'Using svnserve with SASL' chapter</a> in the Subversion book.</p>
-<p>When <a href="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth"
+<p>When <a href="https://svnbook.red-bean.com/en/1.7/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth"
>using svnserve with SSH authentication</a> SSH keys can be used to
work around this limitation of passwords.</p>
@@ -5073,7 +5073,7 @@ revision, and the other is often a tempo
the need for write access.</p>
<p>This limitation only applies to the Berkeley DB backend; the <a
-href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.fsfs"
+href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.fsfs"
>FSFS backend</a> does not exhibit this behaviour.</p>
</div>
Modified: subversion/site/publish/faq.ja.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.ja.html?rev=1891386&r1=1891385&r2=1891386&view=diff
==============================================================================
--- subversion/site/publish/faq.ja.html [utf-8] (original)
+++ subversion/site/publish/faq.ja.html [utf-8] Thu Jul 8 21:54:05 2021
@@ -296,7 +296,7 @@ Subversionには2種類のサーバプ�
1つは <b>svnserv</b>。これは、小さなスタンドアロンプログラムで cvs の pserver に似ている。
もう1つは、<b>mod_dav_svn</b> という特別なモジュールと組み合わせて Apahce <b>httpd-2.0</b> を使うやり方。
<b>svnserve</b> は独自のプロトコルを使うけど、<b>mod_dav_svn</b> は、WebDAV をネットワークプロトコルとして使う。
-より詳しく知りたい場合には、Subversion Book の<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">6章</a>を参照のこと。</p>
+より詳しく知りたい場合には、Subversion Book の<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">6章</a>を参照のこと。</p>
</div>
@@ -314,7 +314,7 @@ Subversionには2種類のサーバプ�
もし、ネットワークから使えるリポジトリを<b>提供</b>したいならば、Apache2か「svnserve」サーバを設定しなければならない。</p>
<p>
-ネットワークからアクセス可能な Subversion サーバの設定方法に関しては、詳細が Subversion Bookの<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">6章</a>に書いてある。
+ネットワークからアクセス可能な Subversion サーバの設定方法に関しては、詳細が Subversion Bookの<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">6章</a>に書いてある。
</p>
</div>
@@ -455,7 +455,7 @@ Win32システムには、シンボリ�
<p>もし、このFAQの残りを読んでも回答を見付けられなければ、以下のリソースをあたってみると良いだろう。</p>
<ul>
- <li><a href="http://svnbook.red-bean.com">The Subversion Book</a></li>
+ <li><a href="https://svnbook.red-bean.com">The Subversion Book</a></li>
<li><a href="mailing-lists.html">Subversion ユーザーズメイリングリスト</a> (<a href="mailto:users@subversion.apache.org">users@subversion.apache.org</a>)
— 注意: このメイリングリストは<a href="#moderation">モデレータ制</a>だから、あなたの投稿が配送されるまでには、少し遅延があるかも。</li>
<li><a href="https://svn.haxx.se/users/">Subversion ユーザーズリストのアーカイブ</a></li>
@@ -510,7 +510,7 @@ Win32システムには、シンボリ�
<p> <a href="http://svn.collab.net/repos/svn/trunk/README">http://svn.collab.net/repos/svn/trunk/README</a>を参照。特に「セクションIV」の「Quickstart Guide」参照のこと。</p>
-<p>もっと詳しい情報を知りたい人は、<a href="http://svnbook.red-bean.com">The Subversion Book</a>の5章を読もう。</p>
+<p>もっと詳しい情報を知りたい人は、<a href="https://svnbook.red-bean.com">The Subversion Book</a>の5章を読もう。</p>
</div>
@@ -597,7 +597,7 @@ Windowsでは「%APPDATA%\Subversion」�
</h3>
<p>簡単な案は、Apache ではなく<b>svnserve</b>サーバを使うこと。
-詳細は、Subversionブックの<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">第6章</a>を参照のこと。</p>
+詳細は、Subversionブックの<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.html">第6章</a>を参照のこと。</p>
<p>でも、もしあなたの管理者がApacheの実行を認めてくれないんだったら、3690番ポートでカスタムサーバプロセスを実行するのも認めてくれそうにないよね!
というわけで、残りの回答は、管理者が既存のSSHインフラを使うことを<i>許可してくれたら</i>、って想定で書きます。</p>
@@ -795,7 +795,7 @@ Berkeley DBマニュアルに書かれ�
<p>リポジトリにアクセスできるユーザの数を、<em>極力</em>少なくしよう。例えば、apache や 'svnserve -d'を特定ユーザで起動し、リポジトリ全体をそのユーザの所有にする。他のユーザには、<tt>file:///</tt>URL経由でのリポジトリアクセスを許可しないようにし、また 'svnlook' や 'svnadmin' は、そのリポジトリ所有者権限でだけ実行されるようにしよう。</p>
<p>もしクライアントが、<tt>file:///</tt> や <tt>svn+ssh://</tt>経由でアクセスするならば、複数ユーザからのアクセスを無効化させる方法は存在しない。
-この場合、<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html">第6章の最終セクション</a>を読んで、下のほうにある「チェックリスト」サイドバーへ十分注意を払おう。
+この場合、<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html">第6章の最終セクション</a>を読んで、下のほうにある「チェックリスト」サイドバーへ十分注意を払おう。
このリストには、このシナリオを安全に行う為の幾つかのステップが概説されている。</p>
<b>注意: SELinux / Fedora Core 3+ / Red Hat Enterpriseをお使いの方々へ</b>
@@ -830,7 +830,7 @@ SubversionをApacheの元で動作させ
<p>特に、リポジトリは、多くの「リードオンリー」操作に対し、2つのツリーを比較する事で対応する。
1つのツリーは、大抵 HEADリビジョンで、もう片方は概ね一時的なトランザクションツリーだ。というわけで、書き込み権限が必要になる。</p>
-<p>この制限は、Berkeley DBをバックエンドを使っている場合にだけ生じ、<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.fsfs">FSFSバックエンド</a>では発生しない。</p>
+<p>この制限は、Berkeley DBをバックエンドを使っている場合にだけ生じ、<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.fsfs">FSFSバックエンド</a>では発生しない。</p>
</div>
@@ -853,7 +853,7 @@ SubversionをApacheの元で動作させ
このコマンドを使うことで、情報を永久に消し去ることが出来るようになるだろう(<a href="https://issues.apache.org/jira/browse/SVN-516">issue 516</a>を参照の事)。</p>
<p>それまでの間は、あなたの取り得る手段としては、<b>svnadmin dump</b>でリポジトリのダンプを取り、そのファイルをパイプ経由で<b>svndumpfilter</b>を通過させ(不正なパスを取り除く)、その出力を<b>svnadmin load</b>コマンドへ読み込ませる、ということになる。
-詳細は、Subversion bookの<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html">第5章</a>を参照の事。</p>
+詳細は、Subversion bookの<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.html">第5章</a>を参照の事。</p>
</div>
@@ -868,11 +868,11 @@ SubversionをApacheの元で動作させ
<p>ログメッセージは、各リビジョンの属性として貼り付けられた上で、リポジトリに中に保存されている。
デフォルトでは、一度コミットされてしまったログメッセージ属性(<em>svn:log</em>)は、変更することが出来ない。
-これは、<a href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html">リビジョン属性</a>(<em>svn:log</em>はその中の一つ)への変更は、以前のプロパティ値を完全に廃棄してしまう為で、この操作が誤って実行されないよう、Subversionは、あなたを守ってくれている、というわけだ。
+これは、<a href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html">リビジョン属性</a>(<em>svn:log</em>はその中の一つ)への変更は、以前のプロパティ値を完全に廃棄してしまう為で、この操作が誤って実行されないよう、Subversionは、あなたを守ってくれている、というわけだ。
とは言え、リビジョン属性を変更する為の方法は、幾つか存在する。</p>
<p>最初の方法は、リビジョン属性の変更を有効にしたいリポジトリ管理者向けのものだ。
-これは「pre-revprop-change」と呼ばれるフックを作ることで実現される(実現方法の詳細に関しては、Subversion book の<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks">このセクション</a>を参照)。
+これは「pre-revprop-change」と呼ばれるフックを作ることで実現される(実現方法の詳細に関しては、Subversion book の<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks">このセクション</a>を参照)。
この「pre-revprop-change」フックは、ログメッセージが変更される前に、古いログへアクセスするので、何らかの方法(例えば、メイルで送る、など)により、このログを保存することは可能だ。
ひとたびリビジョン属性の変更が有効化されれば、<b>svn propedit</b>か<b>svn propset</b>へ--revpropスイッチを引き渡すことでリビジョンのログメッセージ変更が可能になる。例えば、こんな感じ。</p>
@@ -985,7 +985,7 @@ $ svnadmin setlog REPOS_PATH -r N FILE
<li>svnserveやApacheを再起動。</li>
</ol>
-<p>ダンプとロードの方法の詳細に関しては、<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate">Subversion bookのこのセクション</a>を参照のこと。</p>
+<p>ダンプとロードの方法の詳細に関しては、<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate">Subversion bookのこのセクション</a>を参照のこと。</p>
<p><b>注意</b>: Subversion のほとんどのアップグレード時には、ダンプやロードは<i>必要ない</i>。
これが必要になる場合、リリースアナウンスや、新版の CHANGES ファイルで、十分な告知がなされるだろう。
@@ -1368,7 +1368,7 @@ export SVN_SSH
<p>では、新規ファイルはに関してはどうだろう?
生憎、コミットされかかっているファイルに対して、サーバ側で属性を自動的に与える仕組みは用意されていないんだ。
これは、全てのユーザは、ファイルを<tt>svn add</tt>する度、忘れずに、属性を適切に設定せねばならない、ということを意味する。幸い、この作業を補助するクライアントサイドのツールがある。
-Subversion Book の <a href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto">auto-props</a>機能に関して読んでみよう。
+Subversion Book の <a href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto">auto-props</a>機能に関して読んでみよう。
全てのユーザがクライアントの auto-props 設定を適切に行っているかどうかを、あなたは確認する必要がある。</p>
<p>また、ファイル属性を付け忘れた新規ファイルのコミットを拒否する pre-commit フックスクリプトを書くことも可能だ(例えば、<a href="http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/check-mime-type.pl">http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/check-mime-type.pl</a>を参照)。
@@ -1471,7 +1471,7 @@ log.<i><number></i></tt>」。
</h3>
<p>あなたのリポジトリへpost-commiフックスクリプトを加えることにより、何時でも簡単にこれを実現することができる。
-フックスクリプトについて、Subversion Book の<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks">第5章</a>を参照のこと。
+フックスクリプトについて、Subversion Book の<a href="https://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks">第5章</a>を参照のこと。
基本的なアイディアは、その「ライブサイト」を一般的な作業コピーにした上で、post-commit フックスクリプトにより、作業コピー上で 'svn update' を実行させれば良い。</p>
<p>実際には、幾つか注意すべき点がある。
@@ -1614,7 +1614,7 @@ Subversionは透過となるようには
もし、何れかのバイトが0である場合、または、15%以上が非アスキー表示可能文字であった場合、そのファイルはバイナリと判断される。
とはいえ、このヒューリスティックな手法は、将来、改良されるかも。</p>
-<p>ファイルがバイナリだと判断された場合、そのファイルは svn:mime-type 属性へ「application/octet-strem」が設定される(この挙動は、<a href="http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto">auto-props</a>機能を用いることで、または、手動で<tt>svn propset</tt>を実行して属性を設定することで、何時でも上書きが可能だ)。</p>
+<p>ファイルがバイナリだと判断された場合、そのファイルは svn:mime-type 属性へ「application/octet-strem」が設定される(この挙動は、<a href="https://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto">auto-props</a>機能を用いることで、または、手動で<tt>svn propset</tt>を実行して属性を設定することで、何時でも上書きが可能だ)。</p>
<p>Subversionは以下のファイルをテキストとして扱う。</p>
@@ -1727,7 +1727,7 @@ svn: Path 'svn://server/trunk/stuff/*' d
<p>サードパーティのコードに対するローカルな変更管理に対し、サードパーティからのアップグレードも含め、Subversion を使いたいという要求を、しばしば耳にする。
即ち、分岐した自身のブランチを維持しつつ、上層の提供元から公開される新しいリリースも組み入れたいわけだ。
-これは、一般的に<em>ベンダーブランチ</em>と呼ばれていて(この名称は Subversion 以前から使われている)、Subversion を使ってこれを管理するテクニックは、<a href="http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.advanced.vendorbr">ここで説明されている</a>。</p>
+これは、一般的に<em>ベンダーブランチ</em>と呼ばれていて(この名称は Subversion 以前から使われている)、Subversion を使ってこれを管理するテクニックは、<a href="https://svnbook.red-bean.com/en/1.4/svn-book.html#svn.advanced.vendorbr">ここで説明されている</a>。</p>
<p>もし、ベンダーコードがリモートの Subversion リポジトリで管理されているならば、ベンダーコードのコピーを管理に、<a href="https://github.com/francois/piston">Piston</a>が利用できる。</p>
@@ -1935,7 +1935,7 @@ svn cleanup working-copy
<p>Subversion でコミットを行うと、クライアントは、そのコミットが関与したノードのリビジョン番号だけを変化させる。
作業コピーの中にある全てのノードを変化させるわけではない。
これは、最後にコミットした時期に応じて、単一の作業コピー内に於いても、ファイルやサブディレクトリが異なるリビジョンになるかもしれない、ということだ。ある種の操作(例えばディレクトリの属性変更)では、もしリポジトリ内に、より新しいバージョンのノードが存在する場合には、データの喪失を防ぐため、コミットが拒否される。
-詳細は、<a href="http://svnbook.red-bean.com/">Version Control with Subversion</a>の<a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.limits">Mixed revisions have limitations</a>を参照の事。</p>
+詳細は、<a href="https://svnbook.red-bean.com/">Version Control with Subversion</a>の<a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.limits">Mixed revisions have limitations</a>を参照の事。</p>
<p>この問題は、作業コピー内で 'svn update' を実行することにより解消することが出来る。</p></li>
@@ -2035,7 +2035,7 @@ VC++6.0に同梱されている版は、
<pre>
svn import file:///d:/some/path/to/repos/on/d/drive
</pre>
-<p>詳細は Subversion Book の<a href="http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.advanced.reposurls">Repository URLs</a>をどうぞ。
+<p>詳細は Subversion Book の<a href="https://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.advanced.reposurls">Repository URLs</a>をどうぞ。
</p>
</div>
@@ -2202,7 +2202,7 @@ $ svn log
rev 24: (no author) | 2003-07-29 19:28:35 +0200 (Tue, 29 Jul 2003)
</pre></blockquote>
-<p>Apacheに対してアクセス制限を行う為の設定方法は、<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html">Subversion book</a>を参照のこと。</p>
+<p>Apacheに対してアクセス制限を行う為の設定方法は、<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html">Subversion book</a>を参照のこと。</p>
</div>
@@ -2395,7 +2395,7 @@ GNOME KeyringとKWallteのサポート�
しかし、注意してもらいたいのは、そのキャッシュされたパスワードが格納されているディレクトリ(大抵 ~/.subversion/auth)のパーミションは、700に設定されていて、即ち、あなただけが読みだし可能となっている。</p>
<p>とはいえ、もしあなたが本当に気に病んでいるならば、パスワードのキャッシュ機構を、完全に off にすることができる。svn 1.0 クライアントの場合、ランタイム設定ファイルへ 'store-auth-creds = no' と書くだけだ。svn 1.1 以上のクライアントの場合、より狭い範囲にのみ適用される 'store-passwords = no' を使うことができる(つまり、サーバ証明は、まだキャッシュされる)。
-パスワードキャッシングに関するより詳細な説明は、<a href="http://svnbook.red-bean.com/nightly/en/index.html">Nightly Build 版Subversion book</a>の第6章、<a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache">「Client Credentials Caching」</a>を参照のこと。</p>
+パスワードキャッシングに関するより詳細な説明は、<a href="https://svnbook.red-bean.com/nightly/en/index.html">Nightly Build 版Subversion book</a>の第6章、<a href="https://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache">「Client Credentials Caching」</a>を参照のこと。</p>
<p>最後に、CVS は長期に渡り、パスワードを .cvspass ファイルへ保存している、ということを指摘しておこう。
.cvspass に書かれたパスワードは、暗号化されているように見えるけど、実際には、ただ非常に簡単な、本質的には rot13 同等のアルゴリズムでスクランブルされているだけだ。