Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates
 209.85.214.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E640928.4060603@rowe-clan.net>
References: <4E5EA4A2.9060708@rowe-clan.net>
	<4E5EE507.9050603@rowe-clan.net>
	<CAKUrXK5Ni-rR713tSJf4nrasFkECOiXsr6ew9PsnEDDh5KtyuA@mail.gmail.com>
	<4E640928.4060603@rowe-clan.net>
Date: Tue, 6 Sep 2011 10:01:30 -0400
Message-ID: 
 <CAKUrXK64AgasK+zoE4oVKR7_CdEQe5749TNzUoLvEkLzEaLfQg@mail.gmail.com>
Subject: Re: Appropriate patches for 2.2.19 and 2.0.64?
From: Jeff Trawick <trawick@gmail.com>
To: dev@httpd.apache.org
Cc: APR Developer List <dev@apr.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Sep 4, 2011 at 7:26 PM, William A. Rowe Jr. <wrowe@rowe-clan.net> w=
rote:
> On 9/3/2011 2:49 PM, Jeff Trawick wrote:
>>
>> With this fix, I get no testcase failures and this skippage:
>
> Bingo, stared at that code for hours, finally realized I had
> re-extracted a -2.2 labeled patch instead of correcting the -2.0
> patch... argh!!!
>
> Will incorporate the past couple of trunk/2.2 corrections and
> propose for backport... if accepted we'll post it as the official
> apply_to_2.0.64 patch, with or without a .65 tag. =A0Will also suggest
> we tag apr 0.9.20 in the coming few days so if anyone wants to work
> in any other corrections, do so in the very near term.

Any idea when you will have time/inclination to update the 2.0.64
patch?  I expect to have a bit of time to spend either working on the
patch or testing it.

I can take care of T&R of APR 0.9.20 in a couple of days provided that
someone first gets CVE-2011-1928 resolved in that branch.