svn commit: r1305422 - /subversion/site/publish/docs/release-notes/1.8.html

[danielsh]

Author: danielsh
Date: Mon Mar 26 16:10:50 2012
New Revision: 1305422

URL: http://svn.apache.org/viewvc?rev=1305422&view=rev
Log:
* docs/release-notes/1.8.html
  (#verify-issue4129): Some text tweaks by Greg.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1305422&r1=1305421&r2=1305422&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Mon Mar 26 16:10:50 2012
@@ -236,17 +236,17 @@ will error out on a file that the Subver
 <p>Up to 1.7.0, Subversion could create erroneous metadata on nodes in a
 FSFS-backed repository in certain situations involving concurrent commit
 attempts.  (Only <em>metadata</em> was affected; file contents and properties
-was not.)  As of 1.7.1 Subversion <a
-href="http://svn.apache.org/viewvc/subversion/branches/1.6.x/subversion/libsvn_fs_fs/fs_fs.c?rev=1303070&amp;r1=1303069&amp;r2=1303070&amp;view=diff";
->prevents</a> new instances of the corruption, but
-only as of 1.8.0 does 'svnadmin verify' <a
-  
href="http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_fs_fs/tree.c?r1=1304656&amp;r2=1304655&amp;pathrev=1304656";
->detect</a> instances of that corruption in the history of a repository.</p>
+was not.)  As of 1.7.1 Subversion 
+<!-- r1303070 -->
+prevents new instances of the corruption, but
+only as of 1.8.0 does 'svnadmin verify' 
+<!-- r1304656 -->
+detect instances of that corruption in the history of a repository.</p>
 
 <p>The fix to these issues is simple: perform a dump/load cycle.  (As usual,
 svnsync can be used instead of dump/load.)  The cycle can be done with any 
version
 of Subversion, and after the cycle the repository should be served exclusively 
by
-Subversion 1.7.1 and newer (or 1.7.5 and newer) to prevent further instances 
of the
+Subversion 1.7.5 or newer to prevent further instances of the
 bug from entering the repository.</p>
 
 <p>See <a href="../issue4129">this summary of issue #4129</a> for more 
information