You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by rh...@apache.org on 2014/05/08 18:53:52 UTC

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

Author: rhuijben
Date: Thu May  8 16:53:52 2014
New Revision: 1593330

URL: http://svn.apache.org/r1593330
Log:
1.8.html: Fix a bit of non valid xml syntax

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=1593330&r1=1593329&r2=1593330&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Thu May  8 16:53:52 2014
@@ -661,7 +661,7 @@ only as of 1.8.0 does 'svnadmin verify' 
 detect instances of that corruption in the history of a repository.</p>
 
 <p>The fix to these issues is simple: perform a <a
-href=http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate.svnadmin
+href="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