Sorry. That's my fault.

I created a backport branch `1.14.x-r1921505` when nominating the
revision, but forgot to add a `Branch` declaration for the nomination.

Fixed in r1921922.

On 2024/11/18 1:10, Daniel Sahlberg wrote:
> Hi,
> 
> This change doesn't apply cleanly to 1.14.x. It seems r1880967 (and the 
> followup r1884640) added some typemaps which this change builds upon. I don't 
> understand the swig bindings enough to see if we could merge the above two 
> revisions or if that would be an incompatible change to the 1.14.x series (in 
> which case we need a separate backport branch for r1921505).
> 
> Kind regards,
> Daniel
> 
> On 2024/10/24 03:13:18 jun6...@apache.org wrote:
>> Author: jun66j5
>> Date: Thu Oct 24 03:13:17 2024
>> New Revision: 1921524
>>
>> URL: http://svn.apache.org/viewvc?rev=1921524&view=rev
>> Log:
>> * STATUS: Nominate r1921505
>>
>> Modified:
>>     subversion/branches/1.14.x/STATUS
>>
>> Modified: subversion/branches/1.14.x/STATUS
>> URL: 
>> http://svn.apache.org/viewvc/subversion/branches/1.14.x/STATUS?rev=1921524&r1=1921523&r2=1921524&view=diff
>> ==============================================================================
>> --- subversion/branches/1.14.x/STATUS (original)
>> +++ subversion/branches/1.14.x/STATUS Thu Oct 24 03:13:17 2024
>> @@ -58,6 +58,13 @@ Candidate changes:
>>     votes:
>>       +1: jun66j5
>>  
>> + * r1921505
>> +   Make swig-py compatible with SWIG 4.3.0.
>> +   Justification:
>> +     Ditto.
>> +   votes:
>> +     +1: jun66j5
>> +
>>  Veto-blocked changes:
>>  =====================

-- 
Jun Omae <jun6...@gmail.com> (大前 潤)

Reply via email to