Author: svn-role
Date: Wed Nov  9 04:15:02 2022
New Revision: 1905174

URL: http://svn.apache.org/viewvc?rev=1905174&view=rev
Log:
* upcoming.part.html: Automatically regenerated

Modified:
    subversion/site/publish/upcoming.part.html

Modified: subversion/site/publish/upcoming.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/upcoming.part.html?rev=1905174&r1=1905173&r2=1905174&view=diff
==============================================================================
--- subversion/site/publish/upcoming.part.html (original)
+++ subversion/site/publish/upcoming.part.html Wed Nov  9 04:15:02 2022
@@ -96,6 +96,33 @@ Merge the <a href="https://svn.apache.or
      +1: futatuki, stsp, jamessan
 
 ------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1905172";>r1905172</a> | svn-role | 2022-11-09 
04:00:03 +0000 (Wed, 09 Nov 2022) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1877310";>r1877310</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877310";>r1877310</a>
+   Add a test for <a href="/issue-4711">issue #4711</a> &quot;invalid xml file 
produced by svn log --xml
+   --verbose --use-merge-history --search&quot;.
+   Justification:
+     Increase test coverage.
+   Votes:
+     +0: danielsh (with appropriate Skip()/XFail() annotations if needed)
+     +1: hartmannathan, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1905173";>r1905173</a> | svn-role | 2022-11-09 
04:00:04 +0000 (Wed, 09 Nov 2022) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1904167";>r1904167</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1904167";>r1904167</a>
+   swig-py: Fix conditionals by SWIG version and by Python version for proxy
+   code.
+   Justification:
+     swig-py should be built correctly with upcoming SWIG 4.1.0 release.
+   Votes:
+     +1: futatuki, jun66j5, jamessan
+
+------------------------------------------------------------------------
 </pre>
 
 <p>Further changes currently under consideration are listed in each release 
line's 


Reply via email to