Author: danielsh
Date: Fri Feb 20 23:51:15 2015
New Revision: 1661244
URL: http://svn.apache.org/r1661244
Log:
Release notes: add prospective blame (née kidney blame).
* docs/release-notes/1.9.html
(#new-feature-compatibility-table): Add kidney blame entry.
(#kidney-blame): New minor new feature.
* roadmap.html
(#next-release-status): Rename feature.
Modified:
subversion/site/publish/docs/release-notes/1.9.html
subversion/site/publish/roadmap.html
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=1661244&r1=1661243&r2=1661244&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Fri Feb 20 23:51:15 2015
@@ -100,6 +100,12 @@ and what impact these changes may have.<
<th>Minimum Repository</th>
<th>Notes</th></tr>
<tr>
+ <td><a href="prospective-blame">Prospective blame</a></td>
+ <td>1.9</td>
+ <td>1.8</td>
+ <td>any</td>
+ <td></td></tr>
+ <tr>
<td><a href="#FSX">FSX</a></td>
<td>any</td>
<td>1.9</td>
@@ -802,6 +808,34 @@ command is needed.</p>
</div> <!-- three-way-conflict-markers -->
+<div class="h3" id="prospective-blame">
+<h3>Prospective blame
+ <a class="sectionlink" href="#prospective-blame"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>The <tt>blame</tt> command can now show not only when the <em>last</em>
+change to each line of a given file was, but also when the <em>next</em> change
+will be.</p>
+
+<p>For example, to see for each line in revision 3 of README.txt what the
+next revision that changed (or removed) that line would be, run
+<tt>svn blame -r HEAD:3 README.txt</tt>. (You may need to pass a
+<!-- TODO: link is broken (no 1.9 book branch yet) -->
+<a href="http://svnbook.red-bean.com/en/1.9/svn.advanced.pegrevs.html";>peg
+revision</a> if the file had been renamed since r3.)</p>
+
+<p>In the <tt>blame</tt> command, the range <tt>-r M:N</tt> always means
+"display information about the file at revision N". If the range is
+"forward" (M<N) then the normal blame algorithm is used, displaying for each
+line in the file when it was added or last changed; if the range is "reversed"
+(M>N) then the above-described sense is used, describing for each line in rN
+when it was first changed (or deleted) after rN and before rM.</p>
+
+<p class="todo">Add example</p>
+
+</div> <!-- prospective-blame -->
+
</div> <!-- enhancements -->
<div class="h2" id="issues">
Modified: subversion/site/publish/roadmap.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/roadmap.html?rev=1661244&r1=1661243&r2=1661244&view=diff
==============================================================================
--- subversion/site/publish/roadmap.html (original)
+++ subversion/site/publish/roadmap.html Fri Feb 20 23:51:15 2015
@@ -258,12 +258,12 @@ numbering, compatibility, and deprecatio
release</td></tr>
<tr class="task-level-1 in-progress">
- <td class="task-name">Reverse blame</td>
+ <td class="task-name">Prospective blame</td>
<td class="task-status">In Progress</td>
<td>Allows blame to show the *next* revision when each line in file@N was
changed, looking forwards *after* rN. TODO: Backport recent fixes (i.e.
make it do something sensible at all) to 1.9.0; describe in release
- notes. (Was called 'youngest-to-oldest blame'; codename 'kidney
blame'.)</td>
+ notes. (Codename: 'kidney blame'.)</td>
</tr>
<tr><td colspan="3" class="divider">Generic stuff we do for every
