Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 64270 invoked from network); 9 Aug 2004 16:49:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Aug 2004 16:49:13 -0000 Received: (qmail 78992 invoked by uid 500); 9 Aug 2004 16:49:12 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 78879 invoked by uid 500); 9 Aug 2004 16:49:11 -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 78865 invoked by uid 99); 9 Aug 2004 16:49:11 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Date: Mon, 09 Aug 2004 09:49:17 -0700 From: Justin Erenkrantz To: David Reid , dev@apr.apache.org Subject: Re: RC5 Message-ID: In-Reply-To: <4117AA82.60109@jetnet.co.uk> References: <411761A2.4070600@jetnet.co.uk> <10CC0642A21135530B932CA2@[10.0.1.8]> <4117AA82.60109@jetnet.co.uk> X-Mailer: Mulberry/3.1.5 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, score=-0.1 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0-pre1-r21475 X-Spam-Checker-Version: SpamAssassin 3.0.0-pre1-r21475 (2004-06-19) on scotch.ics.uci.edu X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --On Monday, August 9, 2004 5:46 PM +0100 David Reid wrote: >> patch - but users of the tarball won't likely be running buildconf. [If >> you wanted, you could include the new find_apr.m4 in 1.0 - your call.] > > OK. Which version is the one I should be including? I *believe* r1.16 of build/find_apr.m4 should be okay. However, I'd like to see some other people verify that it works now. (It worked here with autoconf 2.13.) > Well, the way things are going I'd suggest that getting those changes into > apr-util should be a priority. I'd look but haven't been too involved with > it all. I'll *try* to take a look later today... > I debated that, but to be honest once we release 1.0.0 any momentum we have > (what very little there remains) will dissipate very quickly - so let's go > for all on the same day. Understood. -- justin