svn commit: r1058289 - /subversion/site/publish/docs/release-notes/1.7.html

[st...@apache.org]

Author: stsp
Date: Wed Jan 12 19:48:41 2011
New Revision: 1058289

URL: http://svn.apache.org/viewvc?rev=1058289&view=rev
Log:
* publish/docs/release-notes/1.7.html
  (patch): Mention the only other known open issue, too.

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=1058289&r1=1058288&r2=1058289&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Wed Jan 12 19:48:41 2011
@@ -319,6 +319,14 @@ to properties (except for <code>svn:merg
 <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3747"
   >issue #3747</a>).</p>
 
+<p>When a patch does not apply cleanly some or all changes listed in the
+patch might be rejected. But <code>svn patch</code> currently does not
+mark files with rejected changes as conflicted (see
+<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3565"
+  >issue #3565</a>). Files which weren't patched successfully can be
+committed without being touched by <code>svn resolve</code> first.
+This problem will be addressed in a future release of Subversion.</p>
+
 <p>A new API for parsing unidiff patch files has been added to
 <code>libsvn_diff</code>. A new API for applying unidiff patches to a
 working copy has been added to <code>libsvn_client</code>.</p>