MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-50160-1339199061-766.24697-0-0@isc.org>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Disposition: inline
References: <RT-Ticket-24697@isc.org>
 <1299141730.28031.246.camel@hp.my.own.domain>
 <20110531041134.GI11600@daedalus.andrew.net.au>
 <rt-3.8.6-50182-1339198860-1866.24697-5-0@isc.org>
 <20120608234357.GE11520@daedalus.andrew.net.au>
 <rt-3.8.6-50160-1339199061-766.24697-0-0@isc.org>
Content-Type: text/html; charset="UTF-8"
Message-ID: <rt-3.8.6-50182-1339199249-1162.24697-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
Content-Length: 782

On Fri Jun 08 23:44:21 2012, apollock@debian.org wrote: <br />
&gt; On Fri, Jun 08, 2012 at 11:41:00PM +0000, Shawn Routhier via RT wrote: <br />
&gt; &gt; With the resolution of 25979 I think this one is <br />
&gt; &gt; also resolved (again changes will be in the <br />
&gt; &gt; next feature release). <br />
&gt; &gt;  <br />
&gt; &gt; If 25979 didn't resolve the issues you can <br />
&gt; &gt; either re-open this one or open a new ticket. <br />
&gt; &gt;  <br />
&gt;  <br />
&gt; Thanks! So by &quot;next feature release&quot; you mean this won't go into 4.2.5, <br />
&gt; it'll go into 4.3 or whatever it's going to be called? <br />
<br />
That is my current plan but I'm checking internal to determine<br />
if we think it should go into a 4.2 or 4.1-ESV.<br />
<br />