subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhuij...@apache.org
Subject svn commit: r1736194 - in /subversion/site/publish/docs/release-notes: 1.8.html 1.9.html
Date Tue, 22 Mar 2016 14:16:12 GMT
Author: rhuijben
Date: Tue Mar 22 14:16:12 2016
New Revision: 1736194

URL: http://svn.apache.org/viewvc?rev=1736194&view=rev
Log:
* site/publish/release-notes/1.8.html
* site/publish/release-notes/1.9.html
  Remove documented limitation that we somehow can't upgrade from 1.0-1.5
  working copies in these releases.

  With the pre-WCNG working copies we updated them on writing, so you could
  even have specific subdirs with an older or newer version without higher
  layers noticing.

  In several cases 1.9 can better upgrade these old working copies than
  1.7-1.8, as our test suite's validations added shortly before releasing 1.9
  showed some limitations in the correctness of the older upgrade code.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html
    subversion/site/publish/docs/release-notes/1.9.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=1736194&r1=1736193&r2=1736194&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Mar 22 14:16:12 2016
@@ -189,19 +189,19 @@ required to run the <tt>svn upgrade</tt>
 metadata to the new format. This command may take a while, and for some users,
 it may be more practical to simply checkout a new working copy.</p>
 
-<p>Subversion 1.8 can only upgrade working copies created with Subversion 1.6
-and Subversion 1.7.</p>
-
 <p><strong>Note:</strong> Subversion 1.8 cannot upgrade working copies
that
-a 1.6 client would have refused to operate upon before an <tt>svn cleanup</tt>
-was run (with a 1.6 client).  In other words, before upgrading to 1.8, a 1.6
-client must be used to run <tt>svn cleanup</tt> on all 1.6 working copies that
-require cleanup.  Likewise, Subversion 1.8 cannot upgrade corrupt 1.6 working
-copies. Unfixable problems can arise from missing or corrupt meta-data inside
-<tt>.svn</tt> directories.  Such damage to the 1.6 working copy is permanent,
-and cannot be fixed even if <tt>svn cleanup</tt> is run prior to the upgrade.</p>
+a 1.6 -or older- client would have refused to operate upon before an
+<tt>svn cleanup</tt>
+was run (with a 1.6 -or older- client).  In other words, before upgrading to
+1.8, an older client must be used to run <tt>svn cleanup</tt> on all working
+copies that require cleanup.  Likewise, Subversion 1.8 cannot upgrade corrupt
+some 1.6 working copies. Unfixable problems can arise from missing or corrupt
+meta-data inside <tt>.svn</tt> directories.  Such damage to the 1.6 working
+copy is permanent, and cannot be fixed even if <tt>svn cleanup</tt> is run
+prior to the upgrade.</p>
 
-<p>If your working copy does not upgrade cleanly, please check out a new one.</p>
+<p>If your working copy does not upgrade cleanly, please check out a new one.
+</p>
 
 </div>  <!-- wc-upgrade -->
 

Modified: subversion/site/publish/docs/release-notes/1.9.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1736194&r1=1736193&r2=1736194&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Tue Mar 22 14:16:12 2016
@@ -151,25 +151,24 @@ and what impact these changes may have.<
 
 <p>Subversion 1.9 uses the same working copy format as Subversion 1.8.</p>
 
-<p>Before using Subversion 1.9 with existing an 1.6 or 1.7 working copy,
-users will be required to run the <tt>svn upgrade</tt> command to upgrade
-working copy metadata to the new format. This command may take a while, and
-for some users, it may be more practical to simply checkout a new working
-copy.</p>
-
-<p>Subversion 1.9 can only upgrade working copies created with Subversion 1.6
-and Subversion 1.7.</p>
+<p>Before using Subversion 1.9 with an existing a Subversion 1.7 or older
+working copy, users will be required to run the <tt>svn upgrade</tt> command
+to upgrade working copy metadata to the new format. This command may take a
+while in some cases, and for some users, it may be more practical to simply
+checkout a new working copy.</p>
 
 <p><strong>Note:</strong> Subversion 1.9 cannot upgrade working copies
that
 a 1.6 client would have refused to operate upon before an <tt>svn cleanup</tt>
 was run (with a 1.6 client).  In other words, before upgrading to 1.9, a 1.6
-client must be used to run <tt>svn cleanup</tt> on all 1.6 working copies that
-require cleanup.  Likewise, Subversion 1.9 cannot upgrade corrupt 1.6 working
-copies. Unfixable problems can arise from missing or corrupt meta-data inside
-<tt>.svn</tt> directories.  Such damage to the 1.6 working copy is permanent,
-and cannot be fixed even if <tt>svn cleanup</tt> is run prior to the upgrade.</p>
+or older client must be used to run <tt>svn cleanup</tt> on all 1.6 or older
+working copies that require cleanup.  Likewise, Subversion 1.9 cannot upgrade
+corrupt working copies. Unfixable problems can arise from missing or corrupt
+meta-data inside <tt>.svn</tt> directories.  Such damage to the working copy
+is permanent, and cannot be fixed even if <tt>svn cleanup</tt> is run prior
+to the upgrade.</p>
 
-<p>If your working copy does not upgrade cleanly, please check out a new one.</p>
+<p>If your working copy does not upgrade cleanly, please check out a new one.
+</p>
 
 </div>  <!-- wc-upgrade -->
 



Mime
View raw message