Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 6224 invoked from network); 18 Feb 2004 20:06:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 18 Feb 2004 20:06:25 -0000 Received: (qmail 62732 invoked by uid 500); 18 Feb 2004 20:06:06 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 62664 invoked by uid 500); 18 Feb 2004 20:06:05 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 62645 invoked from network); 18 Feb 2004 20:06:04 -0000 Received: from unknown (HELO jimsys.jaguNET.com) (209.133.199.10) by daedalus.apache.org with SMTP; 18 Feb 2004 20:06:04 -0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by jimsys.jaguNET.com (Postfix) with ESMTP id 6A8C9214C3A for ; Wed, 18 Feb 2004 15:06:08 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: <30C025BBA30D3343935890628BCCEA321687CA@BOSEXVS2.digitas.com> References: <30C025BBA30D3343935890628BCCEA321687CA@BOSEXVS2.digitas.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jim Jagielski Subject: Re: Time for 2.0.49, WAS: Re: Time for 1.3.30?? Date: Wed, 18 Feb 2004 15:06:07 -0500 To: dev@httpd.apache.org X-Mailer: Apple Mail (2.612) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Manni, What I did was take the latest/working 2.0.x patch (from the PR report), and backported it to 1.3. I didn't patch the 2.x trees at the same time, because I simply forgot. :/ I believe Cliff is doing that as we speak. On Feb 18, 2004, at 2:33 PM, Manni Wood wrote: > Ummm... as the person who created the new bug (by successfully stomping > a years-old one in the same module), I have a particular interest in > the > solution of this bug. I had submitted a patch to the 2.x series on > bugzilla, and, eventually, things died down with no direction, so I > waited for feedback. So is Jim's patch already ported to 2.x? Is there > another forum where this got resolved? Also, in future, should I take > more initiative and submit a complete trio of patches instead of > waiting > for feedback? Helping out is rewarding, but sometimes confusing for > newbies like me. > > Regardless, thanks, all, for helping fix this bug. > > Cheers, > > -Manni > > -----Original Message----- > From: Cliff Woolley [mailto:jwoolley@virginia.edu] > Sent: Wednesday, February 18, 2004 1:33 PM > To: dev@httpd.apache.org > Subject: Re: Time for 2.0.49, WAS: Re: Time for 1.3.30?? > > On Wed, 18 Feb 2004, Sander Striker wrote: > >> In response to this, how do we feel about doing 2.0.49 >> aswell? > > +1, but let's make sure to get the mod_usertrack fix finally committed. > Jim already committed it to 1.3.x as far as I know, and there's no > reason > not to commit it to 2.0.x and 2.1.x except I just kept forgetting to do > so. > > --Cliff > > -- ======================================================================= Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson