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

[rh...@apache.org]

Author: rhuijben
Date: Thu May  8 16:55:19 2014
New Revision: 1593331

URL: http://svn.apache.org/r1593331
Log:
1.8.html: Fix one more 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=1593331&r1=1593330&r2=1593331&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:55:19 2014
@@ -1270,7 +1270,7 @@ and properties. Hence, Subversion 1.6 an
 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 <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</a> into that new repository using 1.8 tooling and to
 finally use the repository with a 1.6 or 1.7 server.
 </p>