Is it still fair for me to think this patch will be
backported to the
new 2.0.61 AKA 'old' 2.0.60 (because of APR issues) or
should I hold out
for 2.0.62? (sounds like a rhetorical question)
Also since I'm new to the development/release cycle used on
this list, I
was wondering if there are other ways to keep the focus on
certain
patches/enhancements without sounding too much like a
nagging/begging
person ;)
-----Oorspronkelijk bericht-----
Van: Jim Jagielski [mailto:jim jaguNET.com]
Verzonden: vrijdag 10 augustus 2007 13:35
Aan: devhttpd.apache.org
Onderwerp: Re: 1.3 bugs
OK, this will for sure not be in 2.0.60 or 2.2.5, but
I will add as a backport for 2.0.61 and 2.2.6...
On Aug 9, 2007, at 6:34 PM, Jim Jagielski wrote:
> Let me look at it in the morning... I'm not planning a
T&R until
> later on in the afternoon, and I'm east coast anyway
>
> Jan van den Berg wrote:
>>
>> This is a multi-part message in MIME format.
>>
>> ------_=_NextPart_001_01C7DAD1.44210627
>> Content-Type: text/plain;
>> charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>>
>> I understand the T&R is coming up.
>> I did notice a drop from 886->843 bugs in the
bug report for 2.x
>> over =
>> the last week. Will there be more fixes for the 2.x
branch before
>> the =
>> T&R (I didn't see a message on the list about
this).
>>
>> I'm just curious because I also submitted a little
patch (41887)
>> some =
>> months ago that is of a great deal of use to myself
(maybe only
>> myself, =
>> but still).
>>
>> Cheers,
>>
>> Jan=20
>>
>>
>> -----Original Message-----
>> From: Jim Jagielski [mailto:jimjaguNET.com]
>> Sent: Thu 2-8-2007 22:30
>> To: devhttpd.apache.org
>> Subject: 1.3 bugs
>> =20
>> I went through and cleared out maybe 200 or so
bugzilla bugs
>> for 1.3... Will start on the 2.x ones tomorrow and
try to
>> clear out most of the crud there... We have some
real old ones
>>
>>
>> ------_=_NextPart_001_01C7DAD1.44210627
>> Content-Type: text/html;
>> charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML
3.2//EN">
>> <HTML>
>> <HEAD>
>> <META HTTP-EQUIV=3D"Content-Type"
CONTENT=3D"text/html; =
>> charset=3Diso-8859-1">
>> <META NAME=3D"Generator"
CONTENT=3D"MS Exchange Server version =
>> 6.5.7651.59">
>> <TITLE>RE: 1.3 bugs</TITLE>
>> </HEAD>
>> <BODY>
>> <!-- Converted from text/plain format -->
>>
>> <P><FONT SIZE=3D2>I understand the
T&R is coming up.<BR>
>> I did notice a drop from 886->843 bugs in
the bug report for
>> 2.x over =
>> the last week. Will there be more fixes for the 2.x
branch before
>> the =
>> T&R (I didn't see a message on the list
about this).<BR>
>> <BR>
>> I'm just curious because I also submitted a little
patch (41887)
>> some =
>> months ago that is of a great deal of use to myself
(maybe only
>> myself, =
>> but still).<BR>
>> <BR>
>> Cheers,<BR>
>> <BR>
>> Jan<BR>
>> <BR>
>> <BR>
>> -----Original Message-----<BR>
>> From: Jim Jagielski [<A =
>> HREF=3D"mailto:jimjaguNET.com">mailto:jimjaguNET.com</A>]<BR>
>> Sent: Thu 2-8-2007 22:30<BR>
>> To: devhttpd.apache.org<BR>
>> Subject: 1.3 bugs<BR>
>> <BR>
>> I went through and cleared out maybe 200 or so
bugzilla bugs<BR>
>> for 1.3... Will start on the 2.x ones tomorrow and
try to<BR>
>> clear out most of the crud there... We have some
real old ones <BR>
>> <BR>
>> </FONT>
>> </P>
>>
>> </BODY>
>> </HTML>
>> ------_=_NextPart_001_01C7DAD1.44210627--
>>
>
>
> --
>
============================================================
==========
> =====
> Jim Jagielski [|] jimjaguNET.com [|] http://
> www.jaguNET.com/
> "If you can dodge a wrench, you can dodge a
ball."
>
|
