Author: stsp
Date: Wed Oct 19 13:23:55 2011
New Revision: 1186197
URL: http://svn.apache.org/viewvc?rev=1186197&view=rev
Log:
* site/publish/docs/release-notes/1.7.html
(wc-ng): Explain that corrupt 1.6 working copies cannot be upgraded.
Modified:
subversion/site/publish/docs/release-notes/1.7.html
Modified: subversion/site/publish/docs/release-notes/1.7.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1186197&r1=1186196&r2=1186197&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Wed Oct 19 13:23:55 2011
@@ -494,8 +494,13 @@ practical to simply checkout a new worki
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.7, a 1.6
client must be used to run <tt>svn cleanup</tt> on all working copies that
-require cleanup. We regret for this limitation, but we had to introduce it in
-order for 1.7 to ship timely and without overcomplicating the internals.</p>
+require cleanup. Likewise, Subversion 1.7 cannot upgrade corrupt 1.6 working
+copies. Unfixsable problems can arise form missing 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>We regret these limitations, but we had to introduce them in order for
+1.7 to ship timely and without overcomplicating the internals.
+If your working copy does not upgrade cleanly, please check out a new one.</p>
<!-- 'sed -ne 5p < .svn/entries' to print `svn info | grep URL` of a 1.4-1.6
working copy. -->
