subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@apache.org
Subject svn commit: r1406995 - /subversion/site/publish/docs/release-notes/1.8.html
Date Thu, 08 Nov 2012 10:17:41 GMT
Author: stefan2
Date: Thu Nov  8 10:17:41 2012
New Revision: 1406995

URL: http://svn.apache.org/viewvc?rev=1406995&view=rev
Log:
* site/public/docs/release-notes/1.8.html
  (): turn "dump / load" into links to the 1.8 svn book describing
  that migration procedure

Suggested by: breser

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=1406995&r1=1406994&r2=1406995&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Thu Nov  8 10:17:41 2012
@@ -325,11 +325,12 @@ 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.5 or newer to prevent further instances of the
-bug from entering the repository.</p>
+<p>The fix to these issues is simple: perform a <a
+href=http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin
+>dump/load cycle</a>.  (As usual, svnsync can be used instead of dump/load.)
+The cycle can be done with any version of Subversion, and after the cycle the
+repository should be served exclusively by Subversion 1.7.5 or newer to prevent
+further instances of the bug from entering the repository.</p>
 
 <p>See <a href="../issue4129">this summary of issue #4129</a> for more
information
 about these problems.</p>
@@ -719,7 +720,8 @@ remain fully supported by Subversion 1.8
 <p>You may use <tt>svnadmin upgrade</tt> to upgrade existing repositories.
 However, to fully benefit from the latest <a href="#fsfs-deltification">repository
size reductions</a>,
 it is recommended to create a new repository, adjust its settings and then
-dump / load or svnsync the content into it.
+<a href=http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin
+>dump / load</a> or svnsync the content into it.
 </p>
 
 </div>  <!-- fsfs-format-6 -->
@@ -812,10 +814,11 @@ improves cache efficiency and can also s
 to read deltified data is the same for file content as for directories
 and properties. Hence, Subversion 1.6 and 1.7 will be able to read
 them but will always write new revisions without that optimization.
-It is therefore perfectly legal to create a pre-1.8-compatible repository
-in 1.8, to enable various deltification options, to dump/load into
-the new repository using 1.8 tooling and to finally use it with a 1.6
-or 1.7 server.
+It is therefore perfectly legal to create a pre-1.8-compatible
+repository in 1.8, to enable various deltification options, to <a 
+href=http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin
+>dump / load</a> into that new repository using 1.8 tooling and to
+finally use it with a 1.6 or 1.7 server.
 </p>
 
 </div>  <!-- fsfs-deltification -->



Mime
View raw message