Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 84294 invoked from network); 28 Jun 2004 08:32:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Jun 2004 08:32:28 -0000 Received: (qmail 83539 invoked by uid 500); 28 Jun 2004 08:32:35 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 83281 invoked by uid 500); 28 Jun 2004 08:32:29 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 83152 invoked by uid 99); 28 Jun 2004 08:32:25 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Message-ID: <00ec01c45cea$9c70b030$7500a8c0@goliath> From: "David Reid" To: "APR Dev List" References: <00b601c45c7a$075764f0$7500a8c0@goliath> <1088370897.32365.137.camel@localhost> Subject: Re: [PROPOSAL] cgi_exec_info_t: detached & addrspace fieldscombined Date: Mon, 28 Jun 2004 09:33:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at jetnet.co.uk X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > On Sun, 2004-06-27 at 20:06 +0100, David Reid wrote: > > Can someone clarify the status of this patch? > > > > I wasn't planning on including it in the 1.0 tarball as I don't see how we > > could test it in time and making an PAI at this late stage isn't a good idea > > is it? > > > > However, in a private reply Jean-Jacques stated that he hoped this to go > > into 2.0.51, which would imply it goes into our 0.9 tree. This is a little > > worrying as we'd then be in the situation whereby 0.9 had something that 1.0 > > didn't... > > > > I'm tempted to say that this should ONLY be applied for 1.1 and upwards > > which would obviously mean that the httpd 2.0 tree wouldn't get the fix - > > can we all say not ideal? > > > > I'd be interested in hearing what people think. > > Since you asked... > > I think we should branch httpd 2.1 into 2.2, and make a new stable > branch. The focus Work on making an APR 1.1 with *any* API changes we > need, and at the same time push 2.1 towards a 2.2 branch. Hopefully in > a month or two, release APR 1.1.0 and HTTPd 2.2.0 with the new APIs and > plenty of new features. As Will Rowe points out this is about APR and not httpd. > I believe this route has more advantages than trying to push such a > feature back into httpd 2.0.X Again, while I may share your views, this is largely irrelevant for this forum :-( david