Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Request to pick up fix with revision 1683266 (swig perl typemap
 update) with next subversion release
To: "dev@subversion.apache.org" <dev@subversion.apache.org>
References: <loom.20160630T115220-151@post.gmane.org>
 <20160630202631.GB46565@jim.stsp.name>
From: Stefan <luke1410@posteo.de>
Message-ID: <22d6df61-150f-3433-4211-e43fb7c10d45@posteo.de>
Date: Sun, 3 Jul 2016 14:21:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <20160630202631.GB46565@jim.stsp.name>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
archived-at: Sun, 03 Jul 2016 12:22:07 -0000

On 6/30/2016 22:26, Stefan Sperling wrote:
> On Thu, Jun 30, 2016 at 11:21:30AM +0000, Ioannis Kappas wrote:
>> Hello,
>>
>> Can you please kindly consider picking up the fix with revision 1683266 
>> (http://svn.apache.org/viewvc?view=revision&revision=1683266) in the 
>> next patch/official subversion release? 
> It has been nominated for 1.9.5. I can't guarantee the fix will
> be in 1.9.5 but I don't see a reason why it shouldn't make it.
> It just needs one more vote from a committer to make it in,
> and no vetoes.

I'm not an expert with SWIG and Perl, but from a plain code change point
of view, this fix seems suspicious to also be applicable to the
1.8-branch, isn't it?

Regards,
Stefan