Author: julianfoad
Date: Thu Jun 20 16:30:27 2013
New Revision: 1495084
URL: http://svn.apache.org/r1495084
Log:
In the 1.8 release notes, explicitly point out that a local move is not
preserved as a move when committed, as I feel some readers would have
optimistically assumed it meant more than it did.
* publish/docs/release-notes/1.8.html
(svn-status-info-moves, moves): Tweak and expand.
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=1495084&r1=1495083&r2=1495084&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Thu Jun 20 16:30:27 2013
@@ -305,13 +305,13 @@ for more information.</p>
</div>
<div class="h4" id="svn-status-info-moves">
-<h4><tt>svn status</tt> and <tt>svn info</tt> now show moves
+<h4><tt>svn status</tt> and <tt>svn info</tt> now show local moves
<a class="sectionlink" href="#svn-status-info-moves"
title="Link to this section">¶</a>
</h4>
<p><tt>svn status</tt> now shows moves in its output.
-See the <a href="#moves">section about moves</a> for more information.</p>
+See the <a href="#moves">section about local moves</a> for more
information.</p>
<p><tt>svn status</tt> shows an extra line for each item involved in a
move:</p>
<pre>$ svn move epsilon/zeta zeta-moved
@@ -323,7 +323,7 @@ A + zeta-moved
$
</pre>
-<p><tt> svn info</tt> shows extra lines for moved items, too.
+<p><tt> svn info</tt> shows extra lines for locally moved items, too.
For example, if the file <tt>beta</tt> was moved to <tt>beta-new</tt>,
<tt>svn info beta</tt> will show the following (some unrelated output
has been omitted in this example):</p>
@@ -784,10 +784,11 @@ See <a href="#svnauthz_accessof">this se
<p>The effect of the <tt>svn move</tt> command is now different
from running <tt>svn copy</tt> followed by <tt>svn delete</tt>.
-Moves are represented as a copy and a delete which are linked to one another.
+Moves are represented within the working copy as a copy and a delete which
+are linked to one another.
These links are shown by <tt>svn status</tt> and <tt>svn info</tt>.</p>
-<p>Some Subversion operations will now treat moved files and directories
+<p>Some Subversion operations will now treat locally moved files and
directories
specially. Behavioural changes include:</p>
<ul>
<li><p><tt>svn move</tt> now refuses to move a
@@ -806,10 +807,17 @@ specially. Behavioural changes include:<
is no longer linked to a deletion.</p></li>
</ul>
-<p>Known issues are:</p>
+<p>Limitations:</p>
+<ul>
+ <li><p>Moves are recorded as such only within the working copy. The link
+ between the copy and the delete is established only when a local move
+ operation is performed, and is lost upon commit.</p></li>
+</ul>
+
+<p>Known issues:</p>
<ul>
<li><p>Tree conflicts involving replacements are currently
- not detected when updating a move (see <a
+ not detected when updating a moved file or directory (see <a
href="http://subversion.tigris.org/issues/show_bug.cgi?id=4318"
>issue #4318</a>).</p></li>
<li><p>Tree conflicts flagged by <tt>svn merge</tt> cannot be automatically