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

[st...@apache.org]

Author: stsp
Date: Tue Sep 18 12:31:16 2012
New Revision: 1387116

URL: http://svn.apache.org/viewvc?rev=1387116&view=rev
Log:
* publish/docs/release-notes/1.8.html: Document 'svn mergeinfo -r'.

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=1387116&r1=1387115&r2=1387116&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Sep 18 12:31:16 2012
@@ -789,6 +789,33 @@ in the given situation.</p>
 
 </div>  <!-- auto-merge -->
 
+<div class="h4" id="mergeinfo-r">
+<h4>'svn mergeinfo' now honors the -r option
+  <a class="sectionlink" href="#mergeinfo-r"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>The <tt>svn mergeinfo</tt> command now honors the <tt>-r</tt> option.
+While the option has always been accepted and documented, it was silently
+ignored, such that <tt>svn mergeinfo</tt> always operated on the entire
+history of the repository.</p>
+
+<p>In Subversion 1.8, the <tt>-r</tt> option restricts the output of
+<tt>svn mergeinfo</tt> to the specified revision range, which is useful
+when determining whether or not a given revision, or range of revisions,
+is eligible for merging, or whether it has already been merged.
+In the following example, r682012 has not been merged from trunk yet,
+while r2682012 has already been merged:</p>
+<pre>
+  $ svn mergeinfo --show-revs=eligible -r 682012 ^/trunk
+  r682012
+  $ svn mergeinfo --show-revs=merged -r 2682012 ^/trunk
+  r2682012
+  $
+</pre>
+
+</div>  <!-- mergeinfo-r -->
+
 </div>  <!-- merge-tracking-enhancements -->
 
 <div class="h3" id="hooks">