You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by mf...@apache.org on 2010/02/11 22:04:42 UTC
svn commit: r909145 [2/6] - in /subversion/site/publish: ./ docs/
docs/community-guide/ docs/release-notes/ style/
Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Thu Feb 11 21:04:38 2010
@@ -1,8 +1,14 @@
-<div class="h1" id="roles" title="roles">
-<h1>Community Roles</h1>
-
-<div class="h2" id="committers" title="committers">
-<h2>Committers</h2>
+<div class="h1" id="roles">
+<h1>Community Roles
+ <a class="sectionlink" href="#roles"
+ title="Link to this section">¶</a>
+</h1>
+
+<div class="h2" id="committers">
+<h2>Committers
+ <a class="sectionlink" href="#committers"
+ title="Link to this section">¶</a>
+</h2>
<p>Committers in the Subversion project are those folks to whom the
right to directly commit changes to our version controlled resources
@@ -18,8 +24,11 @@
>COMMITTERS</a> file lists all committers, both full and partial, and
says the domains for each partial committer.</p>
-<div class="h3" id="full-commit-access" title="full-commit-access">
-<h3>How full commit access is granted</h3>
+<div class="h3" id="full-commit-access">
+<h3>How full commit access is granted
+ <a class="sectionlink" href="#full-commit-access"
+ title="Link to this section">¶</a>
+</h3>
<p>After someone has successfully contributed a few non-trivial
patches, some full committer, usually whoever has reviewed and applied
@@ -63,8 +72,11 @@
</div> <!-- full-commit-access -->
-<div class="h3" id="partial-commit-access" title="partial-commit-access">
-<h3>How partial commit access is granted</h3>
+<div class="h3" id="partial-commit-access">
+<h3>How partial commit access is granted
+ <a class="sectionlink" href="#partial-commit-access"
+ title="Link to this section">¶</a>
+</h3>
<p>A full committer sponsors the partial committer. Usually this
means the full committer has applied several patches to the same area
@@ -108,8 +120,11 @@
</div> <!-- partial-commit-access -->
-<div class="h3" id="contrib-area" title="contrib-area">
-<h3>The contrib/ area</h3>
+<div class="h3" id="contrib-area">
+<h3>The contrib/ area
+ <a class="sectionlink" href="#contrib-area"
+ title="Link to this section">¶</a>
+</h3>
<p>When a tool is accepted into the <i>contrib/</i> area, we
automatically offer its author partial commit access to maintain the
@@ -124,8 +139,11 @@
</div> <!-- contrib-area -->
-<div class="h3" id="obvious-fix" title="obvious-fix">
-<h3>The "obvious fix" rule</h3>
+<div class="h3" id="obvious-fix">
+<h3>The "obvious fix" rule
+ <a class="sectionlink" href="#obvious-fix"
+ title="Link to this section">¶</a>
+</h3>
<p>Any committer, whether full or partial, may commit fixes for
obvious typos, grammar mistakes, and formatting problems wherever they
@@ -156,8 +174,11 @@
</div> <!-- committers -->
-<div class="h2" id="release-manager" title="release-manager">
-<h2>Release Manager</h2>
+<div class="h2" id="release-manager">
+<h2>Release Manager
+ <a class="sectionlink" href="#release-manager"
+ title="Link to this section">¶</a>
+</h2>
<p>The role of the Release Manager in the Subversion project is to
handle the process of getting code stabilized, packaged and released
@@ -187,8 +208,11 @@
</div> <!-- release-manager -->
-<div class="h2" id="patch-manager" title="patch-manager">
-<h2>Patch Manager</h2>
+<div class="h2" id="patch-manager">
+<h2>Patch Manager
+ <a class="sectionlink" href="#patch-manager"
+ title="Link to this section">¶</a>
+</h2>
<p>Subversion usually has a Patch Manager, whose job is to watch the
dev@ mailing list and make sure that no patches "slip through the
Modified: subversion/site/publish/docs/index.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/index.html?rev=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/index.html (original)
+++ subversion/site/publish/docs/index.html Thu Feb 11 21:04:38 2010
@@ -25,8 +25,11 @@
so if you spot errors in them, please feel free to submit
corrections to the relevant owners of the documentation.</p>
-<div class="h2" id="user-manuals" title="user-manuals">
-<h2>Subversion User Manuals</h2>
+<div class="h2" id="user-manuals">
+<h2>Subversion User Manuals
+ <a class="sectionlink" href="#user-manuals"
+ title="Link to this section">¶</a>
+</h2>
<p>If you want to know how to use Subversion, you can find a number of
published user manuals available
@@ -41,8 +44,11 @@
</div> <!-- #user-manuals -->
-<div class="h2" id="guides" title="guides">
-<h2>Community Guides</h2>
+<div class="h2" id="guides">
+<h2>Community Guides
+ <a class="sectionlink" href="#guides"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion community operates at peak efficiency when everyone
honors the various policies which were established by the community
@@ -58,8 +64,11 @@
</div> <!-- #guides -->
-<div class="h2" id="api" title="api">
-<h2>Subversion API</h2>
+<div class="h2" id="api">
+<h2>Subversion API
+ <a class="sectionlink" href="#api"
+ title="Link to this section">¶</a>
+</h2>
<p>Subversion is a collection of modular libraries written in the C
programming language, each of which has a clearly defined
@@ -87,8 +96,11 @@
</div> <!-- #api -->
-<div class="h2" id="release-notes" title="release-notes">
-<h2>Release Notes</h2>
+<div class="h2" id="release-notes">
+<h2>Release Notes
+ <a class="sectionlink" href="#release-notes"
+ title="Link to this section">¶</a>
+</h2>
<p>Here are a set of release notes for the major Subversion releases
thus far:</p>
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=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.2.html (original)
+++ subversion/site/publish/docs/release-notes/1.2.html Thu Feb 11 21:04:38 2010
@@ -18,8 +18,11 @@
<h1 style="text-align: center">Subversion 1.2 Release Notes</h1>
-<div class="h2" id="news" title="news">
-<h2>What's New in Subversion 1.2</h2>
+<div class="h2" id="news">
+<h2>What's New in Subversion 1.2
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
<ul>
<li>Optional locking ("reserved checkouts")</li>
@@ -39,8 +42,11 @@
</div>
-<div class="h2" id="downloading" title="downloading">
-<h2>Downloading</h2>
+<div class="h2" id="downloading">
+<h2>Downloading
+ <a class="sectionlink" href="#downloading"
+ title="Link to this section">¶</a>
+</h2>
<p>Subversion 1.2 is available as source code in three formats:</p>
@@ -67,8 +73,11 @@
</div>
-<div class="h2" id="compatibility" title="compatibility">
-<h2>Compatibility Concerns</h2>
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility"
+ title="Link to this section">¶</a>
+</h2>
<p>Older clients and servers interoperate transparently with 1.2
servers and clients. Of course, some of the new 1.2 features may not
@@ -87,8 +96,11 @@
program written for 1.2 cannot necessarily compile or run against
older libraries.</p>
-<div class="h3" id="output-changes" title="output-changes">
-<h3>Command Line Output Changes</h3>
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>Although the Subversion developers try hard to keep output from the
command line programs compatible between releases, new information
@@ -111,8 +123,11 @@
</div>
-<div class="h3" id="bdb-upgrade" title="bdb-upgrade">
-<h3>Unexpected Berkeley DB Upgrades</h3>
+<div class="h3" id="bdb-upgrade">
+<h3>Unexpected Berkeley DB Upgrades
+ <a class="sectionlink" href="#bdb-upgrade"
+ title="Link to this section">¶</a>
+</h3>
<p>This is not actually related to the Subversion 1.2 release, but it
may affect you if you upgrade to 1.2 via a package distribution
@@ -136,8 +151,11 @@
</div>
-<div class="h2" id="known-bugs" title="known-bugs">
-<h2>Known Bugs</h2>
+<div class="h2" id="known-bugs">
+<h2>Known Bugs
+ <a class="sectionlink" href="#known-bugs"
+ title="Link to this section">¶</a>
+</h2>
<p>Subversion 1.2.3 fixes several bugs in 1.2.1 and 1.2.0 (1.2.2 was a
placeholder release and was never officially blessed). See the <a
@@ -155,11 +173,17 @@
</div>
-<div class="h2" id="new-features" title="new-features">
-<h2>New Features</h2>
-
-<div class="h3" id="locking" title="locking">
-<h3>File Locking (<em>requires new client and server</em>)</h3>
+<div class="h2" id="new-features">
+<h2>New Features
+ <a class="sectionlink" href="#new-features"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="locking">
+<h3>File Locking (<em>requires new client and server</em>)
+ <a class="sectionlink" href="#locking"
+ title="Link to this section">¶</a>
+</h3>
<p>"Locking" is a long-requested feature, often known in other systems
as "reserved checkouts". While Subversion is still primarily a <a
@@ -193,8 +217,11 @@
</div>
-<div class="h3" id="autoversioning" title="autoversioning">
-<h3>Full DAV autoversioning (<em>mod_dav_svn feature</em>)</h3>
+<div class="h3" id="autoversioning">
+<h3>Full DAV autoversioning (<em>mod_dav_svn feature</em>)
+ <a class="sectionlink" href="#autoversioning"
+ title="Link to this section">¶</a>
+</h3>
<p>Autoversioning is a feature whereby generic WebDAV clients can
write to a DeltaV server (like mod_dav_svn), and the server performs
@@ -243,8 +270,11 @@
</div>
-<div class="h3" id="new-switches" title="new-switches">
-<h3>New subcommand switches:</h3>
+<div class="h3" id="new-switches">
+<h3>New subcommand switches:
+ <a class="sectionlink" href="#new-switches"
+ title="Link to this section">¶</a>
+</h3>
<dl>
<dt><tt>svn log --limit N</tt></dt>
<dd>Display only N revisions, then stop. (<em>Note: a 1.2
@@ -290,12 +320,18 @@
</div>
-<div class="h2" id="enhancements" title="enhancements">
-<h2>Enhancements and Bugfixes</h2>
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</a>
+</h2>
-<div class="h3" id="xdelta" title="xdelta">
+<div class="h3" id="xdelta">
<h3>Faster access to old revisions due to xdelta compression
-(<em>server</em>)</h3>
+(<em>server</em>)
+ <a class="sectionlink" href="#xdelta"
+ title="Link to this section">¶</a>
+</h3>
<p>The repository is now using the xdelta differencing algorithm
(instead of vdelta) to store compressed difference data. When you
@@ -318,8 +354,11 @@
</div>
-<div class="h3" id="fsfs" title="fsfs">
-<h3>FSFS repositories are now the default (<em>server</em>)</h3>
+<div class="h3" id="fsfs">
+<h3>FSFS repositories are now the default (<em>server</em>)
+ <a class="sectionlink" href="#fsfs"
+ title="Link to this section">¶</a>
+</h3>
<p>After the tremendous success of FSFS repositories since the 1.1
release, we've changed the <tt>svnadmin create</tt> command to create
@@ -340,9 +379,11 @@
</div>
-<div class="h3" id="win32-password-encryption"
- title="win32-password-encryption">
-<h3>Cached passwords are encrypted on Windows (<em>Windows client</em>)</h3>
+<div class="h3" id="win32-password-encryption">
+<h3>Cached passwords are encrypted on Windows (<em>Windows client</em>)
+ <a class="sectionlink" href="#win32-password-encryption"
+ title="Link to this section">¶</a>
+</h3>
<p>On Windows 2000 and later, the command-line client encrypts the
cached passwords used for authenticating to a remote Subversion server
@@ -366,8 +407,11 @@
</div>
-<div class="h3" id="bugfixes" title="bugfixes">
-<h3>Bugfixes:</h3>
+<div class="h3" id="bugfixes">
+<h3>Bugfixes:
+ <a class="sectionlink" href="#bugfixes"
+ title="Link to this section">¶</a>
+</h3>
<p>More than 50 new bugs fixed. See the <a
href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a> file
for details.</p>
@@ -376,8 +420,11 @@
</div>
-<div class="h2" id="developer-changes" title="developer-changes">
-<h2>Developer Changes</h2>
+<div class="h2" id="developer-changes">
+<h2>Developer Changes
+ <a class="sectionlink" href="#developer-changes"
+ title="Link to this section">¶</a>
+</h2>
<p>The svn_ra.h API has now been "flattened", essentially imitating
the same way the svn_fs.h API hides multiple implementations. Instead
@@ -398,8 +445,11 @@
</div>
-<div class="h2" id="svn-1.0-deprecation" title="svn-1.0-deprecation">
-<h2>Deprecation of 1.0.x Series</h2>
+<div class="h2" id="svn-1.0-deprecation">
+<h2>Deprecation of 1.0.x Series
+ <a class="sectionlink" href="#svn-1.0-deprecation"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion 1.0.x line is no longer supported. This doesn't
mean that your 1.0 installation is doomed; if it works well and is all
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=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.3.html (original)
+++ subversion/site/publish/docs/release-notes/1.3.html Thu Feb 11 21:04:38 2010
@@ -18,8 +18,11 @@
<h1 style="text-align: center">Subversion 1.3 Release Notes</h1>
-<div class="h2" id="news" title="news">
-<h2>What's New in Subversion 1.3</h2>
+<div class="h2" id="news">
+<h2>What's New in Subversion 1.3
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
<ul>
<li>Path-based authorization for svnserve</li>
@@ -42,8 +45,11 @@
</div> <!-- news -->
-<div class="h2" id="downloading" title="downloading">
-<h2>Downloading</h2>
+<div class="h2" id="downloading">
+<h2>Downloading
+ <a class="sectionlink" href="#downloading"
+ title="Link to this section">¶</a>
+</h2>
<p>Subversion 1.3 is available as source code in three formats:</p>
@@ -67,8 +73,11 @@
</div> <!-- downloading -->
-<div class="h2" id="compatibility" title="compatibility">
-<h2>Compatibility Concerns</h2>
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility"
+ title="Link to this section">¶</a>
+</h2>
<p>Older clients and servers interoperate transparently with 1.3
servers and clients. Of course, some of the new 1.3 features may not
@@ -87,8 +96,11 @@
However, a program written for 1.3 cannot necessarily compile or run
against older libraries.</p>
-<div class="h3" id="output-changes" title="output-changes">
-<h3>Command Line Output Changes</h3>
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>Although the Subversion developers try hard to keep output from the
command line programs compatible between releases, new information
@@ -120,8 +132,11 @@
</div> <!-- output-changes -->
-<div class="h3" id="bdb-upgrade" title="bdb-upgrade">
-<h3>Unexpected Berkeley DB Upgrades</h3>
+<div class="h3" id="bdb-upgrade">
+<h3>Unexpected Berkeley DB Upgrades
+ <a class="sectionlink" href="#bdb-upgrade"
+ title="Link to this section">¶</a>
+</h3>
<p>This is not actually related to the Subversion 1.3 release, but it
may affect you if you upgrade to 1.3 via a package distribution
@@ -144,11 +159,17 @@
</div> <!-- bdb-upgrade -->
</div> <!-- compatibility -->
-<div class="h2" id="new-features" title="new-features">
-<h2>New Features</h2>
-
-<div class="h3" id="svnserve-authz" title="svnserve-authz">
-<h3>Path-based authorization for svnserve (<em>requires new server</em>)</h3>
+<div class="h2" id="new-features">
+<h2>New Features
+ <a class="sectionlink" href="#new-features"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="svnserve-authz">
+<h3>Path-based authorization for svnserve (<em>requires new server</em>)
+ <a class="sectionlink" href="#svnserve-authz"
+ title="Link to this section">¶</a>
+</h3>
<p><b>svnserve</b>, the stand-alone Subversion server, is now able to
restrict both read and write access using the same
@@ -183,8 +204,11 @@
</div> <!-- svnserve-authz -->
-<div class="h3" id="dav-logging" title="dav-logging">
-<h3>Operational logging for mod_dav_svn (<em>requires new server</em>)</h3>
+<div class="h3" id="dav-logging">
+<h3>Operational logging for mod_dav_svn (<em>requires new server</em>)
+ <a class="sectionlink" href="#dav-logging"
+ title="Link to this section">¶</a>
+</h3>
<p>The Apache HTTPD-based server (mod_dav_svn) is now able to log
high-level Subversion operations, e.g., "update", "lock", "commit",
@@ -215,8 +239,11 @@
</div> <!-- dav-logging -->
-<div class="h3" id="bindings-improvements" title="bindings-improvements">
-<h3>Major Language Binding Improvements</h3>
+<div class="h3" id="bindings-improvements">
+<h3>Major Language Binding Improvements
+ <a class="sectionlink" href="#bindings-improvements"
+ title="Link to this section">¶</a>
+</h3>
<ul>
<li>It's now possible to build the SWIG bindings from source without
@@ -238,8 +265,11 @@
</div> <!-- bindings-improvements -->
-<div class="h3" id="new-switches" title="new-switches">
-<h3>New subcommand switches</h3>
+<div class="h3" id="new-switches">
+<h3>New subcommand switches
+ <a class="sectionlink" href="#new-switches"
+ title="Link to this section">¶</a>
+</h3>
<dl>
<dt><tt>svn blame --xml [--incremental]</tt></dt>
<dt><tt>svn status --xml [--incremental]</tt></dt>
@@ -266,11 +296,17 @@
</div> <!-- new-features -->
-<div class="h2" id="enhancements" title="enhancements">
-<h2>Enhancements and Bugfixes</h2>
-
-<div class="h3" id="listparentpath" title="listparentpath">
-<h3>Listing available repositories in mod_dav_svn (<em>server</em>)</h3>
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="listparentpath">
+<h3>Listing available repositories in mod_dav_svn (<em>server</em>)
+ <a class="sectionlink" href="#listparentpath"
+ title="Link to this section">¶</a>
+</h3>
<p>The Apache HTTPD-based server can now display (in a web browser)
the collection of repositories exported by the SVNParentPath
@@ -280,8 +316,11 @@
</div> <!-- listparentpath -->
-<div class="h3" id="neon25" title="neon25">
-<h3>Interruptible http(s):// connections (<em>client</em>)</h3>
+<div class="h3" id="neon25">
+<h3>Interruptible http(s):// connections (<em>client</em>)
+ <a class="sectionlink" href="#neon25"
+ title="Link to this section">¶</a>
+</h3>
<p>If built with Neon 0.25.1 or higher, Subversion can be interrupted
during network operations over http:// and https://. This is a
@@ -290,9 +329,12 @@
</div> <!-- neon25 -->
-<div class="h3" id="_svn-hack" title="_svn-hack">
+<div class="h3" id="_svn-hack">
<h3>Official support for Windows '_svn' directories (<em>client and
-language bindings</em>)</h3>
+language bindings</em>)
+ <a class="sectionlink" href="#_svn-hack"
+ title="Link to this section">¶</a>
+</h3>
<p>The "<b>_svn</b>" hack is
now <a
@@ -323,8 +365,11 @@
</div> <!-- _svn-hack -->
-<div class="h3" id="performance" title="performance">
-<h3>Performance improvements (<em>client and server</em>)</h3>
+<div class="h3" id="performance">
+<h3>Performance improvements (<em>client and server</em>)
+ <a class="sectionlink" href="#performance"
+ title="Link to this section">¶</a>
+</h3>
<p><b>svn status</b> is a bit faster, as is any command that involves
tracing long lines of history, such as <b>svn log</b>. See <a
@@ -338,8 +383,11 @@
</div> <!-- performance -->
-<div class="h3" id="apis" title="apis">
-<h3>API improvements (<em>client and server</em>)</h3>
+<div class="h3" id="apis">
+<h3>API improvements (<em>client and server</em>)
+ <a class="sectionlink" href="#apis"
+ title="Link to this section">¶</a>
+</h3>
<p>If you develop a 3rd-party client application that uses Subversion
APIs, you may want to take notice of some new APIs:</p>
@@ -360,8 +408,11 @@
</div> <!-- apis -->
-<div class="h3" id="bugfixes" title="bugfixes">
-<h3>Other bugfixes (<em>client and server</em>)</h3>
+<div class="h3" id="bugfixes">
+<h3>Other bugfixes (<em>client and server</em>)
+ <a class="sectionlink" href="#bugfixes"
+ title="Link to this section">¶</a>
+</h3>
<p>The usual slew of heretofore-unreleased bugfixes. See the
<a href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a>
@@ -369,8 +420,11 @@
</div> <!-- bugfixes -->
-<div class="h3" id="wc-props-change" title="wc-props-change">
-<h3>Changes in the working copy format</h3>
+<div class="h3" id="wc-props-change">
+<h3>Changes in the working copy format
+ <a class="sectionlink" href="#wc-props-change"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.3 features a minor change in the way properties are
stored in the working copy, which reduces the size of some working
@@ -392,8 +446,11 @@
</div> <!-- wc-props-change -->
</div> <!-- enhancements -->
-<div class="h2" id="svn-1.1-deprecation" title="svn-1.1-deprecation">
-<h2>Subversion 1.1.x series no longer supported</h2>
+<div class="h2" id="svn-1.1-deprecation">
+<h2>Subversion 1.1.x series no longer supported
+ <a class="sectionlink" href="#svn-1.1-deprecation"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion 1.1.x line is no longer supported. This doesn't
mean that your 1.1 installation is doomed; if it works well and is all
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=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.4.html (original)
+++ subversion/site/publish/docs/release-notes/1.4.html Thu Feb 11 21:04:38 2010
@@ -18,8 +18,11 @@
<h1 style="text-align: center">Subversion 1.4 Release Notes</h1>
-<div class="h2" id="news" title="news">
-<h2>What's New in Subversion 1.4</h2>
+<div class="h2" id="news">
+<h2>What's New in Subversion 1.4
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
<ul>
<li><tt>svnsync</tt>, a new repository mirroring tool</li>
@@ -43,8 +46,11 @@
</div> <!-- news -->
-<div class="h2" id="compatibility" title="compatibility">
-<h2>Compatibility Concerns</h2>
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility"
+ title="Link to this section">¶</a>
+</h2>
<p>Older clients and servers interoperate transparently with 1.4
servers and clients. Of course, some of the new 1.4 features may not
@@ -60,8 +66,11 @@
However, a program written for 1.4 cannot necessarily compile or run
against older libraries.</p>
-<div class="h3" id="wc-format-change" title="wc-format-change">
-<h3>Working Copy and Repository Format Changes</h3>
+<div class="h3" id="wc-format-change">
+<h3>Working Copy and Repository Format Changes
+ <a class="sectionlink" href="#wc-format-change"
+ title="Link to this section">¶</a>
+</h3>
<p>Due to certain improvements and bugfixes made to the working copy
library, the version number of the working copy format has been
@@ -85,8 +94,11 @@
</div> <!-- wc-format-change -->
-<div class="h3" id="output-changes" title="output-changes">
-<h3>Command Line Output Changes</h3>
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>Although the Subversion developers try hard to keep output from the
command line programs compatible between releases, new information
@@ -104,11 +116,17 @@
</div> <!-- compatibility -->
-<div class="h2" id="new-features" title="new-features">
-<h2>New Features</h2>
-
-<div class="h3" id="svnsync" title="svnsync">
-<h3>svnsync (<em>some features require a 1.4 server</em>)</h3>
+<div class="h2" id="new-features">
+<h2>New Features
+ <a class="sectionlink" href="#new-features"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="svnsync">
+<h3>svnsync (<em>some features require a 1.4 server</em>)
+ <a class="sectionlink" href="#svnsync"
+ title="Link to this section">¶</a>
+</h3>
<p>A new tool — <a
href="http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt"
@@ -133,8 +151,11 @@
</div> <!-- svnsync -->
-<div class="h3" id="wc-improvements" title="wc-improvements">
-<h3>Working copy performance improvements (<em>client</em>)</h3>
+<div class="h3" id="wc-improvements">
+<h3>Working copy performance improvements (<em>client</em>)
+ <a class="sectionlink" href="#wc-improvements"
+ title="Link to this section">¶</a>
+</h3>
<p>The way in which the Subversion client manages your working copy
has undergone radical changes. The <tt>.svn/entries</tt> file is no
@@ -155,8 +176,11 @@
</div> <!-- wc-improvements -->
-<div class="h3" id="bdb-4.4" title="bdb-4.4">
-<h3>BerkeleyDB 4.4 and auto-recovery (<em>server</em>)</h3>
+<div class="h3" id="bdb-4.4">
+<h3>BerkeleyDB 4.4 and auto-recovery (<em>server</em>)
+ <a class="sectionlink" href="#bdb-4.4"
+ title="Link to this section">¶</a>
+</h3>
<p>A common problem with previous versions of Subversion is that
crashed server processes could leave BerkeleyDB-based repositories in
@@ -186,8 +210,11 @@
</div> <!-- bdb-4.4 -->
-<div class="h3" id="svndiff1" title="svndiff1">
-<h3>Binary Delta Encoding Improvements (<em>client and server</em>)</h3>
+<div class="h3" id="svndiff1">
+<h3>Binary Delta Encoding Improvements (<em>client and server</em>)
+ <a class="sectionlink" href="#svndiff1"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion uses the xdelta algorithm to compute differences between
strings of bytes. The output of this algorithm is stored in a custom
@@ -214,8 +241,11 @@
</div> <!-- svndiff1 -->
-<div class="h3" id="new-switches" title="new-switches">
-<h3>New subcommand switches</h3>
+<div class="h3" id="new-switches">
+<h3>New subcommand switches
+ <a class="sectionlink" href="#new-switches"
+ title="Link to this section">¶</a>
+</h3>
This release of Subversion adds a few new switches and options to the
command line client. These are:
@@ -248,11 +278,17 @@
</div> <!-- new-features -->
-<div class="h2" id="enhancements" title="enhancements">
-<h2>Enhancements and Bugfixes</h2>
-
-<div class="h3" id="svnserve" title="svnserve">
-<h3>svnserve as native Windows service (<em>server</em>)</h3>
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="svnserve">
+<h3>svnserve as native Windows service (<em>server</em>)
+ <a class="sectionlink" href="#svnserve"
+ title="Link to this section">¶</a>
+</h3>
The <tt>svnserve</tt> server can now be run as a Windows service. This
allows svnserve to start automatically, at system boot time, without
@@ -263,16 +299,22 @@
</div> <!-- svnserve -->
-<div class="h3" id="keychain" title="keychain">
-<h3>OS X Keychain support (<em>client</em>)</h3>
+<div class="h3" id="keychain">
+<h3>OS X Keychain support (<em>client</em>)
+ <a class="sectionlink" href="#keychain"
+ title="Link to this section">¶</a>
+</h3>
On OS X, the <tt>svn</tt> client now caches passwords in Keychain,
rather than in <tt>~/.subversion/auth/</tt>.
</div> <!-- keychain -->
-<div class="h3" id="apis" title="apis">
-<h3>API improvements (<em>client and server</em>)</h3>
+<div class="h3" id="apis">
+<h3>API improvements (<em>client and server</em>)
+ <a class="sectionlink" href="#apis"
+ title="Link to this section">¶</a>
+</h3>
<p>If you develop a 3rd-party client application that uses Subversion
APIs, you may want to take notice of some new APIs:</p>
@@ -287,8 +329,11 @@
</div> <!-- apis -->
-<div class="h3" id="bugfixes" title="bugfixes">
-<h3>Other bugfixes (<em>client and server</em>)</h3>
+<div class="h3" id="bugfixes">
+<h3>Other bugfixes (<em>client and server</em>)
+ <a class="sectionlink" href="#bugfixes"
+ title="Link to this section">¶</a>
+</h3>
<p>The usual slew of heretofore-unreleased bugfixes, more than 40
overall. See the
@@ -299,8 +344,11 @@
</div> <!-- enhancements -->
-<div class="h2" id="svn-1.2-deprecation" title="svn-1.2-deprecation">
-<h2>Subversion 1.2.x series no longer supported</h2>
+<div class="h2" id="svn-1.2-deprecation">
+<h2>Subversion 1.2.x series no longer supported
+ <a class="sectionlink" href="#svn-1.2-deprecation"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion 1.2.x line is no longer supported. This doesn't
mean that your 1.2 installation is doomed; if it works well and is all
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=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.5.html (original)
+++ subversion/site/publish/docs/release-notes/1.5.html Thu Feb 11 21:04:38 2010
@@ -18,8 +18,11 @@
<h1 style="text-align: center">Subversion 1.5 Release Notes</h1>
-<div class="h2" id="news" title="news">
-<h2>What's New in Subversion 1.5</h2>
+<div class="h2" id="news">
+<h2>What's New in Subversion 1.5
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
<ul>
<li><a href="#merge-tracking"
@@ -61,8 +64,11 @@
</div> <!-- news -->
-<div class="h2" id="compatibility" title="compatibility">
-<h2>Compatibility Concerns</h2>
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility"
+ title="Link to this section">¶</a>
+</h2>
<p>Older clients and servers interoperate transparently with 1.5
servers and clients. However, some of the new 1.5 features (e.g., <a
@@ -83,9 +89,11 @@
and run using 1.5 libraries. However, a program written for 1.5
cannot necessarily compile or run against older libraries.</p>
-<div class="h3" id="new-feature-compatibility-table"
- title="new-feature-compatibility-table">
-<h3>New Feature Compatibility Table</h3>
+<div class="h3" id="new-feature-compatibility-table">
+<h3>New Feature Compatibility Table
+ <a class="sectionlink" href="#new-feature-compatibility-table"
+ title="Link to this section">¶</a>
+</h3>
<table border="1">
<tr>
<th>New Feature</th>
@@ -169,9 +177,11 @@
</div> <!-- new-feature-compatibility-table -->
-<div class="h3" id="wc-and-repos-format-change"
- title="wc-and-repos-format-change">
-<h3>Working Copy and Repository Format Changes</h3>
+<div class="h3" id="wc-and-repos-format-change">
+<h3>Working Copy and Repository Format Changes
+ <a class="sectionlink" href="#wc-and-repos-format-change"
+ title="Link to this section">¶</a>
+</h3>
<p>The working copy format has been upgraded. This means that 1.4 and
older Subversion clients will <em>not</em> be able to work with
@@ -185,8 +195,11 @@
Subversion 1.5. But, repositories are <a href="#repos-upgrades"
><strong>not</strong> upgraded automatically</a>.</p>
-<div class="h4" id="wc-upgrades" title="wc-upgrades">
-<h4>Working Copy Upgrades</h4>
+<div class="h4" id="wc-upgrades">
+<h4>Working Copy Upgrades
+ <a class="sectionlink" href="#wc-upgrades"
+ title="Link to this section">¶</a>
+</h4>
<p><strong>WARNING:</strong> if a Subversion 1.5 client encounters a
pre-1.5 working copy, it will <em>automatically</em> upgrade the
@@ -208,8 +221,11 @@
</div> <!-- wc-upgrades -->
-<div class="h4" id="repos-upgrades" title="repos-upgrades">
-<h4>Repository Upgrades</h4>
+<div class="h4" id="repos-upgrades">
+<h4>Repository Upgrades
+ <a class="sectionlink" href="#repos-upgrades"
+ title="Link to this section">¶</a>
+</h4>
<p>The Subversion 1.5 server works with 1.4 and older repositories,
and it will <em>not</em> upgrade such repositories to 1.5 unless
@@ -238,8 +254,11 @@
</div> <!-- wc-and-repos-format-change -->
-<div class="h3" id="output-changes" title="output-changes">
-<h3>Command Line Output Changes</h3>
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>Although we try hard to keep output from the command line programs
compatible between releases, new information sometimes has to be
@@ -250,8 +269,11 @@
</div> <!-- output-changes -->
-<div class="h3" id="sasl-compatibility" title="sasl-compatibility">
-<h3>SASL and <code>svn://</code> compatibility</h3>
+<div class="h3" id="sasl-compatibility">
+<h3>SASL and <code>svn://</code> compatibility
+ <a class="sectionlink" href="#sasl-compatibility"
+ title="Link to this section">¶</a>
+</h3>
<p>All 1.x clients, with or without Cyrus SASL support, will be able to
authenticate against all 1.x servers that do not have Cyrus SASL enabled.
@@ -272,9 +294,12 @@
</div> <!-- sasl-compatibility -->
-<div class="h3" id="revprops-compatibility" title="revprops-compatibility">
+<div class="h3" id="revprops-compatibility">
<h3>Custom revprops may now need to be examined by <tt>pre-commit</tt>
- hooks</h3>
+ hooks
+ <a class="sectionlink" href="#revprops-compatibility"
+ title="Link to this section">¶</a>
+</h3>
<p>Each revision in Subversion has a set of <q>revision properties</q>
associated with it; in addition to the standard log message, author,
@@ -309,11 +334,17 @@
</div> <!-- compatibility -->
-<div class="h2" id="new-features" title="new-features">
-<h2>New Features</h2>
-
-<div class="h3" id="merge-tracking" title="merge-tracking">
-<h3>Merge tracking (foundational) (<em>client and server</em>)</h3>
+<div class="h2" id="new-features">
+<h2>New Features
+ <a class="sectionlink" href="#new-features"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="merge-tracking">
+<h3>Merge tracking (foundational) (<em>client and server</em>)
+ <a class="sectionlink" href="#merge-tracking"
+ title="Link to this section">¶</a>
+</h3>
<p><em>Merge tracking</em> means Subversion keeps track of what
changes have been merged where. This reduces the overhead involved in
@@ -340,8 +371,11 @@
by Paul Burba</p></li>
</ul>
-<div class="h4" id="mt-overview" title="mt-overview">
-<h4>Overview</h4>
+<div class="h4" id="mt-overview">
+<h4>Overview
+ <a class="sectionlink" href="#mt-overview"
+ title="Link to this section">¶</a>
+</h4>
<p>Subversion's merge tracking is designed to:</p>
@@ -362,8 +396,11 @@
</div> <!-- mt-overview -->
-<div class="h4" id="mt-ui" title="mt-ui">
-<h4>User interface</h4>
+<div class="h4" id="mt-ui">
+<h4>User interface
+ <a class="sectionlink" href="#mt-ui"
+ title="Link to this section">¶</a>
+</h4>
<p>Merging changes from (say) trunk to a branch no longer requires
that you specify the revision range. Instead, each time you want to
@@ -440,8 +477,11 @@
</div> <!-- mt-ui -->
-<div class="h4" id="mt-compatibility" title="mt-compatibility">
-<h4>Merge tracking and compatibility</h4>
+<div class="h4" id="mt-compatibility">
+<h4>Merge tracking and compatibility
+ <a class="sectionlink" href="#mt-compatibility"
+ title="Link to this section">¶</a>
+</h4>
<p>As described earlier, merge-tracking is not supported unless you <a
href="#repos-upgrades" >upgrade the repository</a> as well as the
@@ -459,8 +499,11 @@
</div> <!-- mt-compatibility -->
-<div class="h4" id="mt-known-issues" title="mt-known-issues">
-<h4>Known Issues</h4>
+<div class="h4" id="mt-known-issues">
+<h4>Known Issues
+ <a class="sectionlink" href="#mt-known-issues"
+ title="Link to this section">¶</a>
+</h4>
<p>There are still known issues with merge tracking in 1.5.0. We're
working on the most important ones first, which are:</p>
@@ -543,8 +586,11 @@
</div> <!-- mt-known-issues -->
-<div class="h4" id="mt-further-reading" title="mt-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="mt-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#mt-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>For more on merge-tracking in Subversion 1.5, see:</p>
@@ -565,8 +611,11 @@
</div> <!-- merge-tracking -->
-<div class="h3" id="sparse-checkouts" title="sparse-checkouts">
-<h3>Sparse checkouts (<em>client and server</em>)</h3>
+<div class="h3" id="sparse-checkouts">
+<h3>Sparse checkouts (<em>client and server</em>)
+ <a class="sectionlink" href="#sparse-checkouts"
+ title="Link to this section">¶</a>
+</h3>
<p>Many users have very large trees of which they only want to
checkout certain parts. In previous versions of Subversion,
@@ -578,8 +627,11 @@
replaces <code>-N</code>, and allows users to construct working
copies containing just what's needed, leaving out everything else.</p>
-<div class="h4" id="sc-depth" title="sc-depth">
-<h4>Depth overview</h4>
+<div class="h4" id="sc-depth">
+<h4>Depth overview
+ <a class="sectionlink" href="#sc-depth"
+ title="Link to this section">¶</a>
+</h4>
<p>Each directory now understands the notion of <em>depth</em>, which has
four possible values: <tt>empty</tt>, <tt>files</tt>, <tt>immediates</tt>,
<tt>infinity</tt>. The values are defined as follows:</p>
@@ -613,8 +665,11 @@
</div> <!-- sc-depth -->
-<div class="h4" id="sc-ui" title="sc-ui">
-<h4>User Interface</h4>
+<div class="h4" id="sc-ui">
+<h4>User Interface
+ <a class="sectionlink" href="#sc-ui"
+ title="Link to this section">¶</a>
+</h4>
<p>Affected commands:</p>
<ul>
<li><code>checkout</code></li>
@@ -664,8 +719,11 @@
</div> <!-- sc-ui -->
-<div class="h4" id="sc-compat" title="sc-compat">
-<h4>Compatibility with older servers</h4>
+<div class="h4" id="sc-compat">
+<h4>Compatibility with older servers
+ <a class="sectionlink" href="#sc-compat"
+ title="Link to this section">¶</a>
+</h4>
<p>The new <tt>--depth</tt> feature naturally requires the client to
be 1.5+, and will work most efficiently if the server is also 1.5+.
@@ -687,8 +745,11 @@
</div> <!-- sc-compat -->
-<div class="h4" id="sc-further-reading" title="sc-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="sc-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#sc-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<ul>
<li>The <a
@@ -704,9 +765,11 @@
</div> <!-- sparse-checkouts -->
-<div class="h3" id="interactive-conflict-resolution"
- title="interactive-conflict-resolution">
-<h3>Interactive Conflict Resolution (<em>client</em>)</h3>
+<div class="h3" id="interactive-conflict-resolution">
+<h3>Interactive Conflict Resolution (<em>client</em>)
+ <a class="sectionlink" href="#interactive-conflict-resolution"
+ title="Link to this section">¶</a>
+</h3>
<p>Conflict resolution is now done interactively by the command-line
client for the
@@ -804,8 +867,11 @@
<li><code>update</code></li>
</ul>
-<div class="h4" id="cl-further-reading" title="cl-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="cl-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#cl-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<ul>
<li>The <a
@@ -821,14 +887,20 @@
</div> <!-- changelists -->
-<div class="h3" id="externals" title="externals">
+<div class="h3" id="externals">
<h3>Relative URLs, peg revisions in <tt>svn:externals</tt>
- (<em>client</em>)</h3>
+ (<em>client</em>)
+ <a class="sectionlink" href="#externals"
+ title="Link to this section">¶</a>
+</h3>
<p>Two additions to the <tt>svn:externals</tt> feature</p>
-<div class="h4" id="externals-peg-revs" title="externals-peg-revs">
-<h4>Peg revision syntax for URLs</h4>
+<div class="h4" id="externals-peg-revs">
+<h4>Peg revision syntax for URLs
+ <a class="sectionlink" href="#externals-peg-revs"
+ title="Link to this section">¶</a>
+</h4>
<p><em>Compatibility and the new syntax:</em> For compatibility
reasons, the pre-1.5 svn:externals syntax continues to not understand
@@ -866,8 +938,11 @@
</div> <!-- externals-peg-revisions -->
-<div class="h4" id="externals-relative-urls" title="externals-relative-urls">
-<h4>Support for relative URLs</h4>
+<div class="h4" id="externals-relative-urls">
+<h4>Support for relative URLs
+ <a class="sectionlink" href="#externals-relative-urls"
+ title="Link to this section">¶</a>
+</h4>
<p>Prior to Subversion 1.5, the URLs in an <tt>svn:externals</tt>
specification must be absolute. Now they can be relative. Four
@@ -964,9 +1039,11 @@
</div> <!-- externals-relative-urls -->
-<div class="h4" id="externals-further-reading"
- title="externals-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="externals-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#externals-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>See The <a
href="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
@@ -976,9 +1053,12 @@
</div> <!-- externals -->
-<div class="h3" id="cyrus-sasl" title="cyrus-sasl">
+<div class="h3" id="cyrus-sasl">
<h3>Cyrus SASL support for ra_svn and <tt>svnserve</tt> (<em>client
-and server</em>)</h3>
+and server</em>)
+ <a class="sectionlink" href="#cyrus-sasl"
+ title="Link to this section">¶</a>
+</h3>
<p>From <a
href="http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer">
@@ -1015,9 +1095,12 @@
</div> <!-- cyrus-sasl -->
-<div class="h3" id="fsfs-sharding" title="fsfs-sharding">
+<div class="h3" id="fsfs-sharding">
<h3>Improved support for large deployments on FSFS, via sharding
- (<em>server</em>)</h3>
+ (<em>server</em>)
+ <a class="sectionlink" href="#fsfs-sharding"
+ title="Link to this section">¶</a>
+</h3>
<p>The FSFS filesystem backend stores each revision in its own file, and prior
to Subversion 1.5, all of these files were stored in a common directory in
@@ -1051,9 +1134,12 @@
</div> <!-- fsfs-sharding -->
-<div class="h3" id="fsfs-isolate-immutable" title="fsfs-isolate-immutable">
+<div class="h3" id="fsfs-isolate-immutable">
<h3>Improved FSFS optimizability, via immutable file isolation
- (<em>server</em>)</h3>
+ (<em>server</em>)
+ <a class="sectionlink" href="#fsfs-isolate-immutable"
+ title="Link to this section">¶</a>
+</h3>
<p>The FSFS repositories never change a revision after it is written
to the disk. Although this should allow the operating system to cache
@@ -1076,8 +1162,11 @@
</div> <!-- fsfs-isolate-immutable -->
-<div class="h3" id="webdav-proxy" title="webdav-proxy">
-<h3>WebDAV transparent write-through proxy (<em>server</em>)</h3>
+<div class="h3" id="webdav-proxy">
+<h3>WebDAV transparent write-through proxy (<em>server</em>)
+ <a class="sectionlink" href="#webdav-proxy"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.4 <a
href="http://subversion.tigris.org/svn_1.4_releasenotes.html#svnsync">
@@ -1101,9 +1190,11 @@
caching proxy, in that each slave can respond to all read-only requests
without ever having to relay them to the master backend.</p>
-<div class="h4" id="webdav-proxy-requirements"
- title="webdav-proxy-requirements">
-<h4>Requirements</h4>
+<div class="h4" id="webdav-proxy-requirements">
+<h4>Requirements
+ <a class="sectionlink" href="#webdav-proxy-requirements"
+ title="Link to this section">¶</a>
+</h4>
<ul>
<li>Subversion 1.5 or newer.</li>
<li>Apache HTTP Server 2.2.0 or higher with mod_proxy enabled.
@@ -1113,8 +1204,11 @@
</div> <!-- webdav-proxy-requirements -->
-<div class="h4" id="webdav-proxy-example" title="webdav-proxy-example">
-<h4>Example configuration</h4>
+<div class="h4" id="webdav-proxy-example">
+<h4>Example configuration
+ <a class="sectionlink" href="#webdav-proxy-example"
+ title="Link to this section">¶</a>
+</h4>
<p>Participants:</p>
<ul>
@@ -1174,9 +1268,11 @@
</div> <!-- webdav-proxy-example -->
-<div class="h4" id="webdav-proxy-further-reading"
- title="webdav-proxy-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="webdav-proxy-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#webdav-proxy-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>Additional information about WebDAV proxy support is available <a
href="http://svn.collab.net/repos/svn/trunk/notes/webdav-proxy">in the
@@ -1189,17 +1285,26 @@
</div> <!-- new-features -->
-<div class="h2" id="enhancements" title="enhancements">
-<h2>Enhancements and Bugfixes</h2>
-
-<div class="h3" id="copy-move-improvements" title="copy-move-improvements">
-<h3>Copy/move-related improvements (<em>client and server</em>)</h3>
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="copy-move-improvements">
+<h3>Copy/move-related improvements (<em>client and server</em>)
+ <a class="sectionlink" href="#copy-move-improvements"
+ title="Link to this section">¶</a>
+</h3>
<p>The abilities and behavior of <code>copy</code> and
<code>move</code> operations are significantly improved in 1.5+.</p>
-<div class="h4" id="leverage-copyfrom" title="leverage-copyfrom">
-<h4>Improved copy-handling during updates (<em>client and server</em>)</h4>
+<div class="h4" id="leverage-copyfrom">
+<h4>Improved copy-handling during updates (<em>client and server</em>)
+ <a class="sectionlink" href="#leverage-copyfrom"
+ title="Link to this section">¶</a>
+</h4>
<p>A common problem in older versions of Subversion was the way in
which <code>svn update</code> handled incoming copies and moves.</p>
@@ -1233,8 +1338,11 @@
</div> <!-- leverage-copyfrom -->
-<div class="h4" id="copy-peg-revs" title="copy-peg-revs">
-<h4>Peg revisions (<em>client</em>)</h4>
+<div class="h4" id="copy-peg-revs">
+<h4>Peg revisions (<em>client</em>)
+ <a class="sectionlink" href="#copy-peg-revs"
+ title="Link to this section">¶</a>
+</h4>
<p>Copy and move operations now accept sources with peg ("@")
revisions.</p>
@@ -1245,8 +1353,11 @@
</div> <!-- copy-peg-revs -->
-<div class="h4" id="multi-op-copy-move" title="multi-op-copy-move">
-<h4>Multiple working copy copy/move operations (<em>client</em>)</h4>
+<div class="h4" id="multi-op-copy-move">
+<h4>Multiple working copy copy/move operations (<em>client</em>)
+ <a class="sectionlink" href="#multi-op-copy-move"
+ title="Link to this section">¶</a>
+</h4>
<p>Clients may now perform chained copy/move operations locally on a
single object in a working copy:</p>
@@ -1262,8 +1373,11 @@
</div> <!-- multi-op-copy-move -->
-<div class="h4" id="multi-src-copy" title="multi-src-copy">
-<h4>Improved handling multiple copy/move sources (<em>client</em>)</h4>
+<div class="h4" id="multi-src-copy">
+<h4>Improved handling multiple copy/move sources (<em>client</em>)
+ <a class="sectionlink" href="#multi-src-copy"
+ title="Link to this section">¶</a>
+</h4>
<p>Clients now accept multiple sources for copy and move operations, with
the ability to copy/move each of the sources to the specified directory.
@@ -1291,8 +1405,11 @@
</div> <!-- multi-src-copy -->
-<div class="h4" id="cp-takes-base" title="cp-takes-base">
-<h4>Copy takes -rBASE (<em>client</em>)</h4>
+<div class="h4" id="cp-takes-base">
+<h4>Copy takes -rBASE (<em>client</em>)
+ <a class="sectionlink" href="#cp-takes-base"
+ title="Link to this section">¶</a>
+</h4>
<p>Copy now understands the special revision "BASE" in a working copy
(as in: "<tt>-rBASE</tt>").</p>
@@ -1303,9 +1420,12 @@
</div> <!-- cp-takes-base -->
-<div class="h4" id="cp-mv-intermediate-dirs" title="cp-mv-intermediate-dirs">
+<div class="h4" id="cp-mv-intermediate-dirs">
<h4>Creation of intermediate directories with copy/move
- (<em>client and server</em>)</h4>
+ (<em>client and server</em>)
+ <a class="sectionlink" href="#cp-mv-intermediate-dirs"
+ title="Link to this section">¶</a>
+</h4>
<p>See the section on the new <a href="#intermediate-directories"
>--parents option</a> for more about this.</p>
@@ -1314,9 +1434,11 @@
</div> <!-- copy-move-improvements -->
-<div class="h3" id="cancellation-improvements"
- title="cancellation-improvements">
-<h3>Cancellation improvements (<em>client</em>)</h3>
+<div class="h3" id="cancellation-improvements">
+<h3>Cancellation improvements (<em>client</em>)
+ <a class="sectionlink" href="#cancellation-improvements"
+ title="Link to this section">¶</a>
+</h3>
<p>Clients operations are now significantly more responsive to
cancellation (e.g. via <tt>control-c</tt>). In pre-1.5 releases,
@@ -1326,8 +1448,11 @@
</div> <!-- cancellation-improvements -->
-<div class="h3" id="cmdline" title="cmdline">
-<h3>Command-line client improvements (<em>client</em>)</h3>
+<div class="h3" id="cmdline">
+<h3>Command-line client improvements (<em>client</em>)
+ <a class="sectionlink" href="#cmdline"
+ title="Link to this section">¶</a>
+</h3>
<p>There are far too many enhancements and new options to the
command-line client to list them all here. Aside from all the ones
@@ -1336,8 +1461,11 @@
href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a> file
for a complete list.</p>
-<div class="h4" id="resolve" title="resolve">
-<h4>New "resolve" subcommand replaces "resolved"</h4>
+<div class="h4" id="resolve">
+<h4>New "resolve" subcommand replaces "resolved"
+ <a class="sectionlink" href="#resolve"
+ title="Link to this section">¶</a>
+</h4>
<p>A new <strong><tt>resolve</tt></strong> subcommand replaces the
"<tt>resolved</tt>" subcommand (the latter is deprecated, but still
@@ -1352,9 +1480,11 @@
</div> <!-- resolve -->
-<div class="h4" id="intermediate-directories"
- title="intermediate-directories">
-<h4>Create intermediate directories if asked</h4>
+<div class="h4" id="intermediate-directories">
+<h4>Create intermediate directories if asked
+ <a class="sectionlink" href="#intermediate-directories"
+ title="Link to this section">¶</a>
+</h4>
<p>Add, mkdir, copy, and move take a new
<strong><tt>--parents</tt></strong> option, which makes intermediate
@@ -1366,8 +1496,11 @@
</div> <!-- intermediate-directories -->
-<div class="h4" id="keep-local" title="keep-local">
-<h4>New --keep-local option retains path after delete.</h4>
+<div class="h4" id="keep-local">
+<h4>New --keep-local option retains path after delete.
+ <a class="sectionlink" href="#keep-local"
+ title="Link to this section">¶</a>
+</h4>
<p>Delete (remove) now takes a
<strong><code>--keep-local</code></strong> option to retain its
@@ -1375,8 +1508,11 @@
</div> <!-- keep-local -->
-<div class="h4" id="commit-revprops" title="commit-revprops">
-<h4>Commit now takes a --with-revprop option.</h4>
+<div class="h4" id="commit-revprops">
+<h4>Commit now takes a --with-revprop option.
+ <a class="sectionlink" href="#commit-revprops"
+ title="Link to this section">¶</a>
+</h4>
Commit now takes a <strong><tt>--with-revprop</tt></strong> option
allowing one to set revision properties
@@ -1389,9 +1525,12 @@
</div> <!-- cmdline -->
-<div class="h3" id="dav-modules" title="dav-modules">
+<div class="h3" id="dav-modules">
<h3>Easier to try out experimental <tt>ra_serf</tt> DAV access module
-(<em>client</em>)</h3>
+(<em>client</em>)
+ <a class="sectionlink" href="#dav-modules"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.4 introduced the experimental <tt>ra_serf</tt>
repository access module for accessing HTTP[S] DAV Subversion servers.
@@ -1412,9 +1551,12 @@
</div> <!-- dav-modules -->
-<div class="h3" id="apis" title="apis">
+<div class="h3" id="apis">
<h3>API changes, improvements and language bindings
- (<em>client and server</em>)</h3>
+ (<em>client and server</em>)
+ <a class="sectionlink" href="#apis"
+ title="Link to this section">¶</a>
+</h3>
<p>There are too many new and revised APIs in Subversion 1.5.0 to even
begin to list them all here. See the <a
@@ -1434,8 +1576,11 @@
</div> <!-- apis -->
-<div class="h3" id="bug-fixes" title="bug-fixes">
-<h3>Bug fixes (<em>client and server</em>)</h3>
+<div class="h3" id="bug-fixes">
+<h3>Bug fixes (<em>client and server</em>)
+ <a class="sectionlink" href="#bug-fixes"
+ title="Link to this section">¶</a>
+</h3>
<p>A great many bugs have been fixed. See the 1.5.0 section in the <a
href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a> file
@@ -1445,8 +1590,11 @@
</div> <!-- enhancements -->
-<div class="h2" id="svn-1.3-deprecation" title="svn-1.3-deprecation">
-<h2>Subversion 1.3.x series no longer supported</h2>
+<div class="h2" id="svn-1.3-deprecation">
+<h2>Subversion 1.3.x series no longer supported
+ <a class="sectionlink" href="#svn-1.3-deprecation"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion 1.3.x line is no longer supported. This doesn't
mean that your 1.3 installation is doomed; if it works well and is all
@@ -1457,11 +1605,17 @@
</div> <!-- svn-1.3-deprecation -->
-<div class="h2" id="deps" title="deps">
-<h2>Subversion Dependencies Distribution: Binary Compatibility Issues</h2>
-
-<div class="h3" id="deps-background" title="deps-background">
-<h3>Background</h3>
+<div class="h2" id="deps">
+<h2>Subversion Dependencies Distribution: Binary Compatibility Issues
+ <a class="sectionlink" href="#deps"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="deps-background">
+<h3>Background
+ <a class="sectionlink" href="#deps-background"
+ title="Link to this section">¶</a>
+</h3>
<p>APR 0.9.x and 1.x are binary-incompatible. This means if you are
already using Subversion with APR 0.9.x, and then upgrade your libapr
@@ -1477,8 +1631,11 @@
</div> <!-- deps-background -->
-<div class="h3" id="deps-now" title="deps-now">
-<h3>Subversion 1.5.0 Dependencies Distribution</h3>
+<div class="h3" id="deps-now">
+<h3>Subversion 1.5.0 Dependencies Distribution
+ <a class="sectionlink" href="#deps-now"
+ title="Link to this section">¶</a>
+</h3>
<p>Today, these dependencies are no longer exotic, so our source
distribution contains just Subversion itself. Those building
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=909145&r1=909144&r2=909145&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.6.html (original)
+++ subversion/site/publish/docs/release-notes/1.6.html Thu Feb 11 21:04:38 2010
@@ -18,8 +18,11 @@
<h1 style="text-align: center">Subversion 1.6 Release Notes</h1>
-<div class="h2" id="news" title="news">
-<h2>What's New in Subversion 1.6</h2>
+<div class="h2" id="news">
+<h2>What's New in Subversion 1.6
+ <a class="sectionlink" href="#news"
+ title="Link to this section">¶</a>
+</h2>
<ul>
<li><a href="#auth-related-improvements"
@@ -64,8 +67,11 @@
</div> <!-- news -->
-<div class="h2" id="compatibility" title="compatibility">
-<h2>Compatibility Concerns</h2>
+<div class="h2" id="compatibility">
+<h2>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility"
+ title="Link to this section">¶</a>
+</h2>
<p>Older clients and servers interoperate transparently with 1.6
servers and clients. However, some of the new 1.6 features may not be
@@ -84,9 +90,11 @@
and run using 1.6 libraries. However, a program written for 1.6
cannot necessarily compile or run against older libraries.</p>
-<div class="h3" id="new-feature-compatibility-table"
- title="new-feature-compatibility-table">
-<h3>New Feature Compatibility Table</h3>
+<div class="h3" id="new-feature-compatibility-table">
+<h3>New Feature Compatibility Table
+ <a class="sectionlink" href="#new-feature-compatibility-table"
+ title="Link to this section">¶</a>
+</h3>
<table border="1">
<tr>
<th>New Feature</th>
@@ -115,9 +123,11 @@
</div> <!-- new-feature-compatibility-table -->
-<div class="h3" id="wc-and-fs-format-change"
- title="wc-and-fs-format-change">
-<h3>Working Copy and Repository Filesystem Format Changes</h3>
+<div class="h3" id="wc-and-fs-format-change">
+<h3>Working Copy and Repository Filesystem Format Changes
+ <a class="sectionlink" href="#wc-and-fs-format-change"
+ title="Link to this section">¶</a>
+</h3>
<p>The working copy format has been upgraded. This means that 1.5 and
older Subversion clients will <em>not</em> be able to work with
@@ -131,8 +141,11 @@
Subversion 1.6. But, repositories are <a href="#repos-upgrades"
><strong>not</strong> upgraded automatically</a>.</p>
-<div class="h4" id="wc-upgrades" title="wc-upgrades">
-<h4>Working Copy Upgrades</h4>
+<div class="h4" id="wc-upgrades">
+<h4>Working Copy Upgrades
+ <a class="sectionlink" href="#wc-upgrades"
+ title="Link to this section">¶</a>
+</h4>
<p><strong>WARNING:</strong> if a Subversion 1.6 client encounters a
pre-1.6 working copy, it will <em>automatically</em> upgrade the
@@ -154,8 +167,11 @@
</div> <!-- wc-upgrades -->
-<div class="h4" id="repos-upgrades" title="repos-upgrades">
-<h4>Repository Upgrades</h4>
+<div class="h4" id="repos-upgrades">
+<h4>Repository Upgrades
+ <a class="sectionlink" href="#repos-upgrades"
+ title="Link to this section">¶</a>
+</h4>
<p>The Subversion 1.6 server works with 1.5 and older repositories,
and it will <em>not</em> upgrade such repositories to 1.6 unless
@@ -172,16 +188,22 @@
</div> <!-- wc-and-fs-format-change -->
-<div class="h3" id="output-changes" title="output-changes">
-<h3>Command Line Output Changes</h3>
+<div class="h3" id="output-changes">
+<h3>Command Line Output Changes
+ <a class="sectionlink" href="#output-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>Although we try hard to keep output from the command line programs
compatible between releases, new information sometimes has to be
added. This can break scripts that rely on the exact format of the
output.</p>
-<div class="h4" id="proplist-verbose" title="proplist-verbose">
-<h4>Improved output of <code>svn proplist --verbose</code></h4>
+<div class="h4" id="proplist-verbose">
+<h4>Improved output of <code>svn proplist --verbose</code>
+ <a class="sectionlink" href="#proplist-verbose"
+ title="Link to this section">¶</a>
+</h4>
<p>The output of <code>svn proplist --verbose</code> has been
improved, and <code>svn propget</code> now accepts the <code>--verbose</code>
@@ -201,8 +223,11 @@
</div> <!-- proplist-verbose -->
-<div class="h4" id="svn-status" title="svn-status">
-<h4>Changed output of <code>svn status</code></h4>
+<div class="h4" id="svn-status">
+<h4>Changed output of <code>svn status</code>
+ <a class="sectionlink" href="#svn-status"
+ title="Link to this section">¶</a>
+</h4>
<p>The output of <code>svn status</code> contains the additional seventh
column which informs whether the item is the victim of a tree conflict.
@@ -225,9 +250,12 @@
</div> <!-- svn-status -->
-<div class="h4" id="conflict-summary" title="conflict-summary">
+<div class="h4" id="conflict-summary">
<h4>Conflict summary printed by <code>svn update</code> and
- <code>svn merge</code></h4>
+ <code>svn merge</code>
+ <a class="sectionlink" href="#conflict-summary"
+ title="Link to this section">¶</a>
+</h4>
<code>svn update</code> and <code>svn merge</code> now print
a summary of conflicts upon completion.
@@ -251,11 +279,17 @@
</div> <!-- output-changes -->
-<div class="h3" id="hook-changes" title="hook-changes">
-<h3>Hook Changes</h3>
-
-<div class="h4" id="pre-lock-hook-output" title="pre-lock-hook-output">
-<h4>Changed handling of output of <code>pre-lock</code> hook</h4>
+<div class="h3" id="hook-changes">
+<h3>Hook Changes
+ <a class="sectionlink" href="#hook-changes"
+ title="Link to this section">¶</a>
+</h3>
+
+<div class="h4" id="pre-lock-hook-output">
+<h4>Changed handling of output of <code>pre-lock</code> hook
+ <a class="sectionlink" href="#pre-lock-hook-output"
+ title="Link to this section">¶</a>
+</h4>
<p>The output of <code>pre-lock</code> hook was previously discarded, but now
it is used to specify the names of lock tokens.</p>
@@ -266,18 +300,26 @@
</div> <!-- compatibility -->
-<div class="h2" id="new-features" title="new-features">
-<h2>New Features</h2>
-
-<div class="h3" id="auth-related-improvements" title="auth-related-improvements">
-<h3>Improved handling of authentication data (<em>client</em>)</h3>
+<div class="h2" id="new-features">
+<h2>New Features
+ <a class="sectionlink" href="#new-features"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="auth-related-improvements">
+<h3>Improved handling of authentication data (<em>client</em>)
+ <a class="sectionlink" href="#auth-related-improvements"
+ title="Link to this section">¶</a>
+</h3>
<p><!-- XXX --><em>This section is currently incomplete, please
help write it!</em></p>
-<div class="h4" id="auth-related-improvements-plaintext-passwords"
-title="auth-related-improvements-plaintext-passwords">
-<h4>Prompting before storing passwords in plaintext form</h4>
+<div class="h4" id="auth-related-improvements-plaintext-passwords">
+<h4>Prompting before storing passwords in plaintext form
+ <a class="sectionlink" href="#auth-related-improvements-plaintext-passwords"
+ title="Link to this section">¶</a>
+</h4>
<p>Subversion prompts before storing passwords in plaintext form.</p>
@@ -305,17 +347,21 @@
</div> <!-- auth-related-improvements-plaintext-passwords -->
-<div class="h4" id="auth-related-improvements-kwallet-gnome-keyring"
-title="auth-related-improvements-kwallet-gnome-keyring">
-<h4>Support for storing passwords in KWallet and GNOME Keyring (Unix-like systems)</h4>
+<div class="h4" id="auth-related-improvements-kwallet-gnome-keyring">
+<h4>Support for storing passwords in KWallet and GNOME Keyring (Unix-like systems)
+ <a class="sectionlink" href="#auth-related-improvements-kwallet-gnome-keyring"
+ title="Link to this section">¶</a>
+</h4>
<p>Passwords can be stored in KWallet (KDE 4) and GNOME Keyring.</p>
</div> <!-- auth-related-improvements-kwallet-gnome-keyring -->
-<div class="h4" id="auth-related-improvements-ssl-client-certificate-passphrases"
-title="auth-related-improvements-ssl-client-certificate-passphrases">
-<h4>Support for storing SSL client certificate passphrases</h4>
+<div class="h4" id="auth-related-improvements-ssl-client-certificate-passphrases">
+<h4>Support for storing SSL client certificate passphrases
+ <a class="sectionlink" href="#auth-related-improvements-ssl-client-certificate-passphrases"
+ title="Link to this section">¶</a>
+</h4>
<p>SSL client certificate passphrases can be stored in KWallet, GNOME
Keyring, Mac OS Keychain, a Windows CryptoAPI encrypted form or in plaintext form.</p>
@@ -324,9 +370,11 @@
</div> <!-- auth-related-improvements -->
-<div class="h3" id="repository-root-relative-urls"
- title="repository-root-relative-urls">
-<h3>Repository root relative URLs (<em>client</em>)</h3>
+<div class="h3" id="repository-root-relative-urls">
+<h3>Repository root relative URLs (<em>client</em>)
+ <a class="sectionlink" href="#repository-root-relative-urls"
+ title="Link to this section">¶</a>
+</h3>
<p><!-- XXX --><em>This section is currently incomplete, please
help write it!</em> See the
@@ -339,8 +387,11 @@
</div> <!-- repository-root-relative-urls -->
-<div class="h3" id="externals" title="externals">
-<h3>Improvements to <tt>svn:externals</tt></h3>
+<div class="h3" id="externals">
+<h3>Improvements to <tt>svn:externals</tt>
+ <a class="sectionlink" href="#externals"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.6 adds a couple of new features for users of
<tt>svn:externals</tt>. The include:</p>
@@ -352,9 +403,12 @@
>Support usual shell quoting rules in externals definitions</a></li>
</ul>
-<div class="h4" id="file-externals" title="file-externals">
+<div class="h4" id="file-externals">
<h4>Support for files in <tt>svn:externals</tt>
- (<em>client</em>)</h4>
+ (<em>client</em>)
+ <a class="sectionlink" href="#file-externals"
+ title="Link to this section">¶</a>
+</h4>
<p>
If the URL in a <tt>svn:externals</tt> description refers to a file,
@@ -408,9 +462,12 @@
</div> <!-- file-externals-further-reading -->
-<div class="h4" id="shell-quoting-externals" title="shell-quoting-externals">
+<div class="h4" id="shell-quoting-externals">
<h4>Support usual shell quoting rules in externals definitions
- (<em><a href="/issues/show_bug.cgi?id=2461">issue 2461</a></em>, client)</h4>
+ (<em><a href="/issues/show_bug.cgi?id=2461">issue 2461</a></em>, client)
+ <a class="sectionlink" href="#shell-quoting-externals"
+ title="Link to this section">¶</a>
+</h4>
<p><!-- XXX -->Need to document possible incompatibilities (see
<a href="/ds/viewMessage.do?dsForumId=462&dsMessageId=86142">this
@@ -418,9 +475,11 @@
</div> <!-- shell-quoting-externals -->
-<div class="h4" id="file-externals-further-reading"
- title="file-externals-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="file-externals-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#file-externals-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>See The <a
href="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html"
@@ -430,8 +489,11 @@
</div> <!-- file-externals -->
-<div class="h3" id="tree-conflicts" title="tree-conflicts">
-<h3>Detection of tree conflicts (<em>client</em>)</h3>
+<div class="h3" id="tree-conflicts">
+<h3>Detection of tree conflicts (<em>client</em>)
+ <a class="sectionlink" href="#tree-conflicts"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.6 recognizes a new kind of conflict, known as a
"tree conflict". Such conflicts manifest at the level
@@ -454,9 +516,11 @@
no changes.</p>
-<div class="h4" id="tree-conflicts-further-reading"
- title="tree-conflicts-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="tree-conflicts-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#tree-conflicts-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>See the <a
href="http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html"
@@ -466,8 +530,11 @@
</div> <!-- tree-conflicts -->
-<div class="h3" id="filesystem-improvements" title="filesystem-improvements">
-<h3>Filesystem Storage Improvements</h3>
+<div class="h3" id="filesystem-improvements">
+<h3>Filesystem Storage Improvements
+ <a class="sectionlink" href="#filesystem-improvements"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.6 contains several improvements to both the Berkeley DB and FSFS
backends. These are designed to improve storage space, and can result in
@@ -483,10 +550,13 @@
>BDB repositories: Forward deltas</a></li>
</ul>
-<div class="h4" id="rep-sharing" title="rep-sharing">
+<div class="h4" id="rep-sharing">
<h4>Sharing multiple common representations
(<em><a href="/issues/show_bug.cgi?id=2286">issue 2286</a></em>,
- <em>server</em>)</h4>
+ <em>server</em>)
+ <a class="sectionlink" href="#rep-sharing"
+ title="Link to this section">¶</a>
+</h4>
<p>When using many branches and merging between them often, it is common to
have files with similar lines of history which contain the exact same content.
In the past, Subversion has stored these files as deltas against previous
@@ -498,8 +568,11 @@
</div> <!-- rep-sharing -->
-<div class="h4" id="fsfs-packing" title="fsfs-packing">
-<h4>FSFS repositories: Packing completed shards (<em>server</em>)</h4>
+<div class="h4" id="fsfs-packing">
+<h4>FSFS repositories: Packing completed shards (<em>server</em>)
+ <a class="sectionlink" href="#fsfs-packing"
+ title="Link to this section">¶</a>
+</h4>
<p>Subversion 1.5 introduced the ability for FSFS repositories to be
<em><a href="svn_1.5_releasenotes.html#fsfs-sharding">sharded</a></em> into
@@ -519,8 +592,11 @@
</div> <!-- fsfs-packing -->
-<div class="h4" id="fsfs-memcached" title="fsfs-memcached">
-<h4>FSFS repositories: Support for Memcached (<em>server</em>)</h4>
+<div class="h4" id="fsfs-memcached">
+<h4>FSFS repositories: Support for Memcached (<em>server</em>)
+ <a class="sectionlink" href="#fsfs-memcached"
+ title="Link to this section">¶</a>
+</h4>
<p><!-- XXX --><a href="http://www.danga.com/memcached/">Memcached</a> can
cache data of FSFS repositories.</p>
@@ -530,8 +606,11 @@
</div> <!-- fsfs-memcached -->
-<div class="h4" id="bdb-forward-deltas" title="bdb-forward-deltas">
-<h4>BDB repositories: Forward deltas (<em>server</em>)</h4>
+<div class="h4" id="bdb-forward-deltas">
+<h4>BDB repositories: Forward deltas (<em>server</em>)
+ <a class="sectionlink" href="#bdb-forward-deltas"
+ title="Link to this section">¶</a>
+</h4>
<p>Newly created BDB repositories now use forward deltas instead of reverse
deltas. <code>svnadmin upgrade</code> can be used to make older repositories
@@ -543,8 +622,11 @@
</div> <!-- filesystem-improvements -->
-<div class="h3" id="ctypes-python-bindings" title="ctypes-python-bindings">
-<h3>Ctypes Python Bindings</h3>
+<div class="h3" id="ctypes-python-bindings">
+<h3>Ctypes Python Bindings
+ <a class="sectionlink" href="#ctypes-python-bindings"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.6 introduces a new python binding for the Subversion API. The
new binding makes use of the ctypes library to present the standard API along
@@ -574,12 +656,17 @@
</div> <!-- new-features -->
-<div class="h2" id="enhancements" title="enhancements">
-<h2>Enhancements and Bugfixes</h2>
-
-<div class="h3" id="improved-interactive-conflict-resolution"
- title="improved-interactive-conflict-resolution">
-<h3>Improved interactive conflict resolution (<em>client</em>)</h3>
+<div class="h2" id="enhancements">
+<h2>Enhancements and Bugfixes
+ <a class="sectionlink" href="#enhancements"
+ title="Link to this section">¶</a>
+</h2>
+
+<div class="h3" id="improved-interactive-conflict-resolution">
+<h3>Improved interactive conflict resolution (<em>client</em>)
+ <a class="sectionlink" href="#improved-interactive-conflict-resolution"
+ title="Link to this section">¶</a>
+</h3>
<p>Interactive conflict resolution supports new <code>display-conflict</code>,
<code>mine-conflict</code> and <code>theirs-conflict</code> options.</p>
@@ -619,9 +706,11 @@
</div> <!-- improved-interactive-conflict-resolution -->
-<div class="h3" id="sparse-directory-exclusion"
- title="sparse-directory-exclusion">
-<h3>Sparse directory exclusion</h3>
+<div class="h3" id="sparse-directory-exclusion">
+<h3>Sparse directory exclusion
+ <a class="sectionlink" href="#sparse-directory-exclusion"
+ title="Link to this section">¶</a>
+</h3>
<p>In Subversion 1.6, the <code>--set-depth</code> parameter to <code>svn
update</code> has grown a new value—<em>exclude</em>. This value tells
@@ -639,9 +728,11 @@
leaves around, and of course leaves any intermediate directories required to
reach those files, too.</p>
-<div class="h4" id="sparse-directory-exclusion-further-reading"
- title="sparse-directory-exclusion-further-reading">
-<h4>Further reading</h4>
+<div class="h4" id="sparse-directory-exclusion-further-reading">
+<h4>Further reading
+ <a class="sectionlink" href="#sparse-directory-exclusion-further-reading"
+ title="Link to this section">¶</a>
+</h4>
<p>See this <a href="http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html">blog post</a> for more examples and information.</p>
@@ -649,9 +740,11 @@
</div> <!-- sparse-directory-exclusion -->
-<div class="h3" id="svnserve-logging"
- title="svnserve-logging">
-<h3>Logging support for svnserve (<em>server</em>)</h3>
+<div class="h3" id="svnserve-logging">
+<h3>Logging support for svnserve (<em>server</em>)
+ <a class="sectionlink" href="#svnserve-logging"
+ title="Link to this section">¶</a>
+</h3>
<p><code>svnserve</code> now accepts the <code>--log-file</code> option which
allows to specify the file used for logging.</p>
@@ -659,9 +752,11 @@
</div> <!-- svnserve-logging -->
-<div class="h3" id="historical-uris"
- title="historical-uris">
-<h3>New public 'historical' HTTP URI syntax for mod_dav_svn (<em>server</em>)</h3>
+<div class="h3" id="historical-uris">
+<h3>New public 'historical' HTTP URI syntax for mod_dav_svn (<em>server</em>)
+ <a class="sectionlink" href="#historical-uris"
+ title="Link to this section">¶</a>
+</h3>
<p>mod_dav_svn now supports a new public URI syntax for
examining older versions of files or directories. The intent here is
@@ -694,8 +789,11 @@
</div> <!-- historical-uris -->
-<div class="h3" id="cmdline" title="cmdline">
-<h3>Command-line client improvements (<em>client</em>)</h3>
+<div class="h3" id="cmdline">
+<h3>Command-line client improvements (<em>client</em>)
+ <a class="sectionlink" href="#cmdline"
+ title="Link to this section">¶</a>
+</h3>
<p>There are far too many enhancements and new options to the
command-line client to list them all here. Aside from all the ones
@@ -704,8 +802,11 @@
href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a> file
for a complete list.</p>
-<div class="h4" id="log-multiple-args" title="log-multiple-args">
-<h4>log can take multiple revisions</h4>
+<div class="h4" id="log-multiple-args">
+<h4>log can take multiple revisions
+ <a class="sectionlink" href="#log-multiple-args"
+ title="Link to this section">¶</a>
+</h4>
<p>The <code>svn log</code> command can now take multiple revision arguments
in one invocation. Both the -c and -r arguments are supported.</p>
@@ -733,8 +834,11 @@
</div> <!-- log-multiple-args -->
-<div class="h4" id="trust-server-cert" title="trust-server-cert">
-<h4>--trust-server-cert option</h4>
+<div class="h4" id="trust-server-cert">
+<h4>--trust-server-cert option
+ <a class="sectionlink" href="#trust-server-cert"
+ title="Link to this section">¶</a>
+</h4>
<p>Option added to <code>svn</code> and <code>svnsync</code>, so that
non-interactive operations can work with self-signed certificates not
@@ -775,9 +879,12 @@
</div> <!-- cmdline -->
-<div class="h3" id="apis" title="apis">
+<div class="h3" id="apis">
<h3>API changes, improvements and language bindings
- (<em>client and server</em>)</h3>
+ (<em>client and server</em>)
+ <a class="sectionlink" href="#apis"
+ title="Link to this section">¶</a>
+</h3>
<p>The <tt>pre-lock</tt> hook can now specify the lock-token string
via the hook's stdout; see <a
@@ -804,8 +911,11 @@
</div> <!-- apis -->
-<div class="h3" id="bug-fixes" title="bug-fixes">
-<h3>Bug fixes (<em>client and server</em>)</h3>
+<div class="h3" id="bug-fixes">
+<h3>Bug fixes (<em>client and server</em>)
+ <a class="sectionlink" href="#bug-fixes"
+ title="Link to this section">¶</a>
+</h3>
<p>A great many bugs have been fixed. See the 1.6.0 section in the <a
href="http://svn.collab.net/repos/svn/trunk/CHANGES">CHANGES</a> file
@@ -815,8 +925,11 @@
</div> <!-- enhancements -->
-<div class="h2" id="svn-1.4-deprecation" title="svn-1.4-deprecation">
-<h2>Subversion 1.4.x series no longer supported</h2>
+<div class="h2" id="svn-1.4-deprecation">
+<h2>Subversion 1.4.x series no longer supported
+ <a class="sectionlink" href="#svn-1.4-deprecation"
+ title="Link to this section">¶</a>
+</h2>
<p>The Subversion 1.4.x line is no longer supported. This doesn't
mean that your 1.4 installation is doomed; if it works well and is all
@@ -827,8 +940,11 @@
</div> <!-- svn-1.4-deprecation -->
-<div class="h2" id="sqlite" title="sqlite">
-<h2>New Dependency: SQLite</h2>
+<div class="h2" id="sqlite">
+<h2>New Dependency: SQLite
+ <a class="sectionlink" href="#sqlite"
+ title="Link to this section">¶</a>
+</h2>
<p>We now require <a href="http://www.sqlite.org/">SQLite</a> to build both
the server and client. We recommend 3.6.13 or greater, but work with