Author: gstein
Date: Fri Jul 8 22:49:03 2011
New Revision: 1144533
URL: http://svn.apache.org/viewvc?rev=1144533&view=rev
Log:
Reserver <code> for actual programming code. Normally, we should be using
the <tt> element.
* site/publish/docs/release-notes/1.7.html: switch to <tt>
Modified:
subversion/site/publish/docs/release-notes/1.7.html
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=1144533&r1=1144532&r2=1144533&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Fri Jul 8 22:49:03 2011
@@ -35,7 +35,7 @@ describes what is planned for the releas
<li><a href="#wc-ng"
>Working Copy Metadata Storage Improvements</a></li>
<li><a href="#svnrdump"
- >New remote dumpfile tool: <code>svnrdump</code></a></li>
+ >New remote dumpfile tool: <tt>svnrdump</tt></a></li>
<li><a href="#httpv2"
>Improved HTTP protocol usage</a></li>
<li><a href="#patch"
@@ -130,7 +130,7 @@ via calls to the <code>svn_ra.h</code> i
<td>1.7</td>
<td>any (dump)<br>1.7 (load)</td>
<td>any</td>
- <td><code>svnrdump load</code> should only be used with 1.7 servers
+ <td><tt>svnrdump load</tt> should only be used with 1.7 servers
to avoid a race condition (see <a
href="#svnrdump">below</a>).</td></tr>
<tr>
<td><a href="#patch">svn patch</a></td>
@@ -143,7 +143,7 @@ via calls to the <code>svn_ra.h</code> i
<td>1.7</td>
<td>1.7</td>
<td>any</td>
- <td>Fixes a race condition in <code>svnsync</code> (<a
+ <td>Fixes a race condition in <tt>svnsync</tt> (<a
href="http://subversion.tigris.org/issues/show_bug.cgi?id=3546";
>issue #3546</a>).</td></tr>
<tr>
@@ -163,7 +163,7 @@ via calls to the <code>svn_ra.h</code> i
<td>Purely server-side configuration. file:// access in 1.7 clients will
use the default settings.</td></tr>
<tr>
- <td colspan="5"><sup>1</sup>Reminder: when using the <code>file://</code>
+ <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
repository access method, the Subversion program is both the client
<em>and</em> the server.</td></tr>
</table>
@@ -180,17 +180,17 @@ via calls to the <code>svn_ra.h</code> i
compatible between releases, new information sometimes has to be
added. This can break scripts that rely on the exact format of the
output. For this reason, we encourage programs which consume the output
-of the commandline client to consider using the <code>--xml</code> option,
+of the commandline client to consider using the <tt>--xml</tt> option,
or accessing Subversion through the various bindings interfaces.</p>
<!-- Insert items here, of the following form:
<div class="h4" id="foo">
-<h4>Improved output of <code>svn foo</code>
+<h4>Improved output of <tt>svn foo</tt>
<a class="sectionlink" href="#foo"
title="Link to this section">¶</a>
</h4>
-<p>The output of <code>svn foo</code> has been improved. The following
+<p>The output of <tt>svn foo</tt> has been improved. The following
example illustrates these changes.</p>
<pre>
@@ -206,12 +206,12 @@ example illustrates these changes.</p>
-->
<div class="h4" id="multi-update">
-<h4>Improved output of <code>svn update</code> for multiple working copies
+<h4>Improved output of <tt>svn update</tt> for multiple working copies
<a class="sectionlink" href="#multi-update"
title="Link to this section">¶</a>
</h4>
-<p>Improvements have been made to the output of <code>svn update</code>
+<p>Improvements have been made to the output of <tt>svn update</tte>
when updating multiple working copies at once (see
<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3693";
>issue #3693</a>). Below is an example of the new output:</p>
@@ -233,13 +233,13 @@ when updating multiple working copies at
</div> <!-- multi-update -->
<div class="h4" id="diff-properties">
-<h4><code>svn diff</code> now shows property changes as unidiff
+<h4><tt>svn diff</tt> now shows property changes as unidiff
<a class="sectionlink" href="#diff-properties"
title="Link to this section">¶</a>
</h4>
-<p><code>svn diff</code> now shows textual property changes in unidiff format,
-except for <code>svn:mergeinfo</code> properties.
+<p><tt>svn diff</tt> now shows textual property changes in unidiff format,
+except for <tt>svn:mergeinfo</tt> properties.
Below is an example of the new output:</p>
<pre>
@@ -277,7 +277,7 @@ Below is an example of the new output:</
title="Link to this section">¶</a>
</h4>
-<p>The output of <code>svn</code> now contains an error number or warning
+<p>The output of <tt>svn</tt> now contains an error number or warning
number with every error. The following example illustrates these changes.</p>
<pre>
@@ -411,8 +411,8 @@ copy metadata system (see
<p>A key feature of the changes introduced in Subversion 1.7 is the
centralization of working copy metadata storage into a single location.
-Instead of a <code>.svn</code> directory in every directory in the working
-copy, Subversion 1.7 working copies have just one <code>.svn</code>
+Instead of a <tt>.svn</tt> directory in every directory in the working
+copy, Subversion 1.7 working copies have just one <tt>.svn</tte>
directory—in the root of the working copy. This directory includes
(among other things) an SQLite-backed database which contains all of the
metadata Subversion needs for that working copy.</p>
@@ -446,13 +446,13 @@ result in working copy corruption.</p>
working copy. Historically, these have been called <em>text-bases</em>, but
in Subversion 1.7, they have received a new name, and a new home. With the
centralization of metadata, the text-bases have been renamed
-<em>pristines</em>, and are now located in the same <code>.svn</code>
+<em>pristines</em>, and are now located in the same <tt>.svn</tt>
directory as the working copy metadata.</p>
<p>The pristines are stored by checksum in a sharded format. Any files
in the working copy which have the same pristine content will now share
references to the pristine store, making such working copies slightly
-smaller. Running <code>svn cleanup</code> will remove any pristines which
+smaller. Running <tt>svn cleanup</tt> will remove any pristines which
are no longer needed by the current state of the working copy.</p>
</div>
@@ -468,7 +468,7 @@ In previous releases of Subversion, Subv
the working copy to the new format when a write operation was performed.
Subversion 1.7, however, will make this a manual step. Before using
Subversion 1.7 with their working copies, users will be required
-to run a new command, <code>svn upgrade</code> to update the metadata to the
+to run a new command, <tt>svn upgrade</tt> to update the metadata to the
new format. This command may take a while, and for some users, it may be more
practical to simply checkout a new working copy.</p>
@@ -508,22 +508,22 @@ old protocol when connecting to a Subver
</div> <!-- httpv2 -->
<div class="h3" id="svnrdump">
-<h3>New remote dumpfile tool: <code>svnrdump</code> (<em>client</em>)
+<h3>New remote dumpfile tool: <tt>svnrdump</tt> (<em>client</em>)
<a class="sectionlink" href="#svnrdump"
title="Link to this section">¶</a>
</h3>
<p>Subversion 1.7 adds a new tool to the client's toolbox:
-<code>svnrdump</code>. <code>svnrdump</code> replicates the functionality of
-<code>svnadmin dump</code> and <code>svnadmin load</code>, but works on
+<tt>svnrdump</tt>. <tt>svnrdump</tt> replicates the functionality of
+<tt>svnadmin dump</tt> and <tt>svnadmin load</tt>, but works on
remote repositories, instead of needing administrator (local filesystem) access
to the source or target repository.</p>
-<p>Note that <code>svnrdump load</code> can suffer from a race condition
+<p>Note that <tt>svnrdump load</tt> can suffer from a race condition
in its locking algorithm when run against a 1.6 or earlier server.
This is the same problem that the new <a href="#atomic-revprops"
>atomic revprop changes feature</a> fixes for
-<code>svnsync</code> (see <a
+<tt>svnsync</tt> (see <a
href="http://subversion.tigris.org/issues/show_bug.cgi?id=3546";
>issue #3546</a>), and the same <a href="#atomic-revprops">server-side
workaround</a> is available.</p>
@@ -531,35 +531,35 @@ workaround</a> is available.</p>
</div> <!-- svnrdump -->
<div class="h3" id="patch">
-<h3>New feature: <code>svn patch</code> (<em>client</em>)
+<h3>New feature: <tt>svn patch</tt> (<em>client</em>)
<a class="sectionlink" href="#patch"
title="Link to this section">¶</a>
</h3>
-<p>Subversion 1.7 features a new subcommand called <code>svn patch</code>
+<p>Subversion 1.7 features a new subcommand called <tt>svn patch</tt>
which can apply patch files in unidiff format (as produced by
-<code>svn diff</code> and other diff tools) to a working copy.</p>
+<tt>svn diff</tt> and other diff tools) to a working copy.</p>
-<p><code>svn patch</code> will apply unidiff changes to existing files just
+<p><tt>svn patch</tt> will apply unidiff changes to existing files just
like third party patch tools.
It will also add newly created files to version control, and delete files
and directories which are left empty after patching.
Keywords and newlines are also handled automatically if the
-<code>svn:keywords</code> and <code>svn:eol-style</code> properties are
+<tt>svn:keywords</tt> and <tt>svn:eol-style</tt> properties are
set on patched files.</p>
-<p><code>svn diff</code> will now produce unidiff output for Subversion
-property changes, and <code>svn patch</code> is able to apply these changes
-to properties (except for <code>svn:mergeinfo</code>, see
+<p><tt>svn diff</tt> will now produce unidiff output for Subversion
+property changes, and <tt>svn patch</tt> is able to apply these changes
+to properties (except for <tt>svn:mergeinfo</tt>, see
<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3747";
>issue #3747</a>).</p>
<p>When a patch does not apply cleanly some or all changes listed in the
-patch might be rejected. But <code>svn patch</code> currently does not
+patch might be rejected. But <tt>svn patch</tt> currently does not
mark files with rejected changes as conflicted (see
<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3565";
>issue #3565</a>). Files which weren't patched successfully can be
-committed without being touched by <code>svn resolve</code> first.
+committed without being touched by <tt>svn resolve</tt> first.
This problem will be addressed in a future release of Subversion.</p>
<p>A new API for parsing unidiff patch files has been added to
@@ -600,7 +600,7 @@ for a complete list.</p>
<a class="sectionlink" href="#log-diff"
title="Link to this section">¶</a>
</h4>
-<p><code>svn log</code> accepts the new <strong><tt>--diff</tt></strong>
+<p><tt>svn log</tt> accepts the new <strong><tt>--diff</tt></strong>
option which causes it to show changes committed in a revision as
a unified diff. Below is example output:</p>
<pre>
@@ -636,7 +636,7 @@ a unified diff. Below is example output:
<a class="sectionlink" href="#update-parents"
title="Link to this section">¶</a>
</h4>
-<p><code>svn update</code> now accepts the <strong><tt>--parents</tt></strong>
+<p><tt>svn update</tt> now accepts the <strong><tt>--parents</tt></strong>
option. This option removes the need to manually create missing parent
directories when adding additional items to a sparse working copy.</p>
@@ -659,9 +659,9 @@ working copy required creating each file
<a class="sectionlink" href="#svn-relocate"
title="Link to this section">¶</a>
</h4>
-<p>A new <code>svn relocate</code> subcommand has been added.
+<p>A new <tt>svn relocate</tt> subcommand has been added.
It points a working copy to a different repository root URL, serving
-the same purpose as the old <code>svn switch --relocate</code> syntax
+the same purpose as the old <tt>svn switch --relocate</tt> syntax
which has now been deprecated.
</div> <!-- svn-relocate -->
@@ -670,14 +670,14 @@ which has now been deprecated.
<a class="sectionlink" href="#switch-ancestry-check"
title="Link to this section">¶</a>
</h4>
-<p><code>svn switch</code> now checks that the working copy item being
+<p><tt>svn switch</tt> now checks that the working copy item being
switched shares common version control history with the URL to which
it is being switched.</p>
<p>This change was made to protect users from the unpleasant side
effects of oft-mistyped switch commands, such as accidentally
-running <code>svn switch ^/branches</code> when you instead meant to
-run <code>svn switch ^/branches/<em>SOME-BRANCH</em></code>. As of
+running <tt>svn switch ^/branches</tt> when you instead meant to
+run <tt>svn switch ^/branches/<em>SOME-BRANCH</em></tt>. As of
version 1.7, Subversion will check to see if the source URL and the
target working copy item are ancestrally related and, if they do not,
the switch operation will fail with an error.</p>
@@ -700,7 +700,7 @@ overlap.</p>
<p>As noted in the previous example's error message, this ancestry
check — which does come at some performance cost — may be
disabled by passing the <strong><tt>--ignore-ancestry</tt></strong>
-option to the <code>svn switch</code> command.</p>
+option to the <tt>svn switch</tt> command.</p>
</div> <!-- switch-ancestry-check -->
<div class="h4" id="diff-show-copies-as-adds">
@@ -708,14 +708,14 @@ option to the <code>svn switch</code> co
<a class="sectionlink" href="#diff-show-copies-as-adds"
title="Link to this section">¶</a>
</h4>
-<p>When <code>svn diff</code> shows a copied file, it usually shows how the
+<p>When <tt>svn diff</tt> shows a copied file, it usually shows how the
copied file differs from the file it was copied from.
Sometimes this isn't the desired form of output. There are situations where
a copied file needs to appear in its entirety, for instance when producing
a patch file to be applied elsewhere with a patch tool (such as
-<a href="#patch"><code>svn patch</code></a>).</p>
+<a href="#patch"><tt>svn patch</tt></a>).</p>
-<p>In Subversion 1.7, <code>svn diff</code> takes a new
+<p>In Subversion 1.7, <tt>svn diff</tt> takes a new
<strong><tt>--show-copies-as-adds</tt></strong> option which causes copied
files to be shown in their entirety, just like newly added files are shown.</p>
@@ -726,34 +726,34 @@ files to be shown in their entirety, jus
<a class="sectionlink" href="#diff-git"
title="Link to this section">¶</a>
</h4>
-<p><code>svn diff</code> takes a new
+<p><tt>svn diff</tt> takes a new
<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";
>git-diff</a>.</p>
-<p><code>svn diff --git</code> is intended to produce patches which are
+<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";
>git-apply</a>, but there are limitations due to differences between
Subversion and git:
<ul>
- <li><code>svn diff</code> currently cannot display rename information.
+ <li><tt>svn diff</tt> currently cannot display rename information.
Renames are always shown as a copy and a delete.</li>
<li>All paths in patches are shown relative to the repository root to
avoid ambiguity. It is possible that the numbers of leading path
components on the left and right side of the patch differ,
- for instance if a diff between <code>/trunk</code> and
- <code>/branches/mybranch</code> is shown.
+ for instance if a diff between <tt>/trunk</tt> and
+ <tt>/branches/mybranch</tt> is shown.
This may prevent git-apply from applying such patches without
modification.</li>
</ul>
</p>
<p>In a future release of Subversion,
-<a href="#patch"><code>svn patch</code></a> will receive support for the
-extra annotations produced by <code>svn diff --git</code>, so that additions,
+<a href="#patch"><tt>svn patch</tt></a> will receive support for the
+extra annotations produced by <tt>svn diff --git</tt>, so that additions,
copies, renames, and deletions can be handled explicitly rather than
implicitly.</p>
@@ -767,7 +767,7 @@ implicitly.</p>
<a class="sectionlink" href="#svn-help-merge"
title="Link to this section">¶</a>
</h4>
-<p>The help text for the <code>svn merge</code> command has been enhanced.
+<p>The help text for the <tt>svn merge</tt> command has been enhanced.
It now explains common use cases and includes small examples, making it
more useful for quick reference.
</div> <!-- svn-help-merge -->
@@ -844,16 +844,16 @@ for details.</p>
used for accessing HTTP-based repositories. You can still build and use the
<a href="http://www.webdav.org/neon/";>neon</a> library, as you always have, and
configure which library the client should use on
-a default or host-by-host basis by setting the <code>http-library</code>
-variable in the client-side <code>servers</code> configuration file
-(<code>~/.subversion/servers</code>).</p>
+a default or host-by-host basis by setting the <tt>http-library</tt>
+variable in the client-side <tt>servers</tt> configuration file
+(<tt>~/.subversion/servers</tt>).</p>
<div class="notice">
<p>Note that
<a href="http://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 <code>httpd.conf</code>
+<p>The <strong>MaxKeepAliveRequests</strong> option in <tt>httpd.conf</tt>
needs to be increased from 100 (the default) to <b>at least</b> 1000
(there is no reason why it could not be 10000).
This will improve performance by allowing serf clients to use fewer
@@ -876,7 +876,7 @@ growth of httpd server logs than neon cl
<p>In the past, when the Subversion client encountered an HTTP redirect
response from the server, it displayed an obtuse, and rarely-useful error
message. Subversion 1.7 improves the situation by following permanent
-redirects for <code>svn update</code> and <code>svn info</code>, and providing
+redirects for <tt>svn update</tt> and <tt>svn info</tt>, and providing
a more useful error message on temporary redirects.</p>
</div> <!-- http-redirects -->
@@ -889,7 +889,7 @@ a more useful error message on temporary
<p>Revprop changes are now handled atomically.
This fixes a known race condition in the locking algorithm used by
-<code>svnsync</code> (see <a
+<tt>svnsync</tt> (see <a
href="http://subversion.tigris.org/issues/show_bug.cgi?id=3546";
>issue #3546</a>). It is possible to fix the svnsync race condition
even for pre-1.7 svnsync clients by installing the pre-revprop-change hook
@@ -920,7 +920,7 @@ file for a complete list.</p>
<p>Merges no longer record mergeinfo (describing the merge) on subtrees (that
have their own explicit mergeinfo), if the subtree was unaffected by the merge.
-This should greatly reduce the number of spurious <code>svn:mergeinfo</code>
+This should greatly reduce the number of spurious <tt>svn:mergeinfo</tt>
property changes for users who have large numbers of sutrees with explicit
mergeinfo.</p>
@@ -953,7 +953,7 @@ diff from the merge source and those tha
'housekeeping' changes.</p>
<p>Below is an example of the new output, showing notifications about
-application of a diff to the file <code>lib/src/psi.c</code> and mergeinfo
+application of a diff to the file <tt>lib/src/psi.c</tt> and mergeinfo
changes resulting from this merge.</p>
<pre>
@@ -976,13 +976,13 @@ changes resulting from this merge.</p>
title="Link to this section">¶</a>
</h4>
-<p>To prevent unnecessary conflicts, <code>svn merge</code> will now fail
+<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";
>mixed-revision working copy</a>.</p>
<p>A mixed-revision working copy will need to be updated with
-<code>svn update</code> before a merge can be performed into it.
+<tt>svn update</tt> before a merge can be performed into it.
This restriction has always existed during merges using the
<strong><tt>--reintegrate</tt></strong> option and it is now the default
behaviour for every type of merge.</p>
@@ -991,7 +991,7 @@ behaviour for every type of merge.</p>
<strong><tt>--allow-mixed-revisions</tt></strong> which disables the
check for a mixed-revision working copy, except for reintegrate merges.
Using this option is <strong>not</strong> recommended.
-Please use <code>svn update</code> instead.</p>
+Please use <tt>svn update</tt> instead.</p>
</div> <!-- merge-mixed-rev-wc -->
@@ -1001,12 +1001,12 @@ Please use <code>svn update</code> inste
title="Link to this section">¶</a>
</h4>
-<p>The <code>svn mergeinfo</code> subcommand now flags revisions wich are
-partially merged to a target with the <code>'*'</code> decorator. A revision
+<p>The <tt>svn mergeinfo</tt> subcommand now flags revisions wich are
+partially merged to a target with the <tt>'*'</tt> decorator. A revision
may be partially merged due to non-inheritable mergeinfo on the target or
because of explicit mergeinfo on some subtree of the target. The latter case
-is ignored by default, but may be considered by using the new <code>--depth
-</code> and <code>-R</code> options for <code>svn mergeinfo</code>.</p>
+is ignored by default, but may be considered by using the new <tt>--depth
+</tt> and <tt>-R</tt> options for <tt>svn mergeinfo</tt>.</p>
</div> <!-- svn-mergeinfo-enhancements -->
@@ -1016,8 +1016,8 @@ is ignored by default, but may be consid
title="Link to this section">¶</a>
</h4>
-<p>Merges performed with the <code>--record-only</code> option now apply
-<code>svn:mergeinfo</code> diffs from the merge source.</p>
+<p>Merges performed with the <tt>--record-only</tt> option now apply
+<tt>svn:mergeinfo</tt> diffs from the merge source.</p>
</div> <!-- svn-merge-record-only -->
@@ -1071,10 +1071,10 @@ three times the sum of all /trunk sizes
server is a reasonable indication for a performance-optimal cache size.
</p>
-<p><code>svnserve</code> introduces a new <code>--memory-cache-size</code>
-/ <code>-M</code> command line parameter to override the default cache
-size. For <code>mod_dav_svn</code>, a 10 GB cache configuration in
-<code>http.conf</code> looks like this</p>
+<p><tt>svnserve</tt> introduces a new <tt>--memory-cache-size</tt>
+/ <tt>-M</tt> command line parameter to override the default cache
+size. For <tt>mod_dav_svn</tt>, a 10 GB cache configuration in
+<tt>http.conf</tt> looks like this</p>
<pre>
<IfModule dav_svn_module>
@@ -1084,7 +1084,7 @@ size. For <code>mod_dav_svn</code>, a 10
<p>As a side-effect, the memory consumption becomes more predictable
in many usage scenarios since there is less need to gather and pre-process
-data. Please note that a cache size of <code>0</code> will deactivate the
+data. Please note that a cache size of <tt>0</tt> will deactivate the
new caching facilities and cause the server to fall back to 1.6 caching
mechanisms.</p>
@@ -1108,15 +1108,15 @@ connected with very limited bandwidth, y
compression rate to squeeze a little more data through the network at
the expense of significantly higher server CPU loads. If the server's NIC
is not a bottleneck, you may consider lowering the compression level to
-<code>1</code> or <code>2</code> for 100 Mb clients and to <code>0</code>
+<tt>1</tt> or <tt>2</tt> for 100 Mb clients and to <tt>0</tt>
(compression off) for a network with predominately 1 Gb clients.</p>
-<p>To that end, <code>svnserve</code> accepts the new optional
-<code>--compression</code> or <code>-c</code> command line parameter.
-<code>mod_dav_svn</code> supports the feature as well but its impact is
+<p>To that end, <tt>svnserve</tt> accepts the new optional
+<tt>--compression</tt> or <tt>-c</tt> command line parameter.
+<tt>mod_dav_svn</tt> supports the feature as well but its impact is
limited since over HTTP, network data compression is used only in certain
cases to begin with. The optional module parameter
-<code>SVNCompressionLevel</code> controls it:</p>
+<tt>SVNCompressionLevel</tt> controls it:</p>
<pre>
<IfModule dav_svn_module>
@@ -1134,8 +1134,8 @@ cases to begin with. The optional module
title="Link to this section">¶</a>
</h3>
-<p>The svn diff algorithm, which is at the core of <code>diff</code>,
-<code>merge</code> and <code>blame</code>, has been optimized to process
+<p>The svn diff algorithm, which is at the core of <tt>diff</tt>,
+<tt>merge</tt> and <tt>blame</tt>, has been optimized to process
identical prefix and suffix lines more efficiently. This speeds up those
operations, especially for large files when the changes are contained in
a limited part of the files.</p>
@@ -1180,7 +1180,7 @@ were hard to find and build, and not oft
Today, this is no longer a problem, so we have discontinued shipping the
companion dependency tarballs. If you still want to get some of the required
Subversion dependencies before building, you can run the
-<code>get-deps.sh</code> script in the root of the unpacked archive.</p>
+<tt>get-deps.sh</tt> script in the root of the unpacked archive.</p>
</div> <!-- deps -->
@@ -1217,7 +1217,7 @@ sites are now the canonical source for S
</div> <!-- asf-mirrors -->
<div class="h3" id="contrib">
-<h3>No longer shipping <code>contrib/</code>
+<h3>No longer shipping <tt>contrib/</tt>
<a class="sectionlink" href="#contrib"
title="Link to this section">¶</a>
</h3>
@@ -1229,7 +1229,7 @@ tools in the main repository has decreas
tool authors to host their contributions at one of a number of external
hosting platforms. For this reason, and the potentially uncertain nature of
some of the licenses on these scripts, we have stopped shipping the
-<code>contrib/</code> directory in the release tarballs. For the time being,
+<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
repository</a>.</p>
