Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 38503 invoked by uid 500); 28 Feb 2001 16:01:18 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 38486 invoked from network); 28 Feb 2001 16:01:17 -0000 Errors-To: Message-ID: <024601c0a19f$9b1090c0$96c0b0d0@roweclan.net> From: "William A. Rowe, Jr." To: References: <20010228164235.D74373@deejai2.mch.fsc.net> Subject: Re: IPv6 in apache-1.3? Date: Wed, 28 Feb 2001 10:00:43 -0600 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N From: "Martin Kraemer" Sent: Wednesday, February 28, 2001 9:42 AM > Some time ago, we decided on trying to integrate the KAME patch into > 1.3.x -- should we do that after 1.3.19? What do you think? > (A colleague of mine keeps patching apache releases over and over again, > integrating the KAME patch; it would save him a lot of work too) If you want to be the maintainer, I suppose that could work. But I'd just ask us to wait 2 weeks to see what fallout occurs from early adopters of 1.3.19 - I just noticed bug 7331 which portends of a leak somewhere around SSI. As soon as we have a stable tree, and no we have introduced no new problems, I'd be happy to test the patch on Win32 to assure it's a no-op. We would need to emblazon the server that we only support that specific IPv6 mechanism, no support for Win32, Netware, etc, and ask those folks to wait for 2.0 where all the new protocol stuff is going on inside of APR. Bill