Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 94135 invoked from network); 20 Jan 2010 04:05:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2010 04:05:25 -0000 Received: (qmail 87123 invoked by uid 500); 20 Jan 2010 04:05:25 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 86732 invoked by uid 500); 20 Jan 2010 04:05:24 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 86724 invoked by uid 99); 20 Jan 2010 04:05:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 04:05:23 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [72.167.82.88] (HELO p3plsmtpa01-08.prod.phx3.secureserver.net) (72.167.82.88) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 20 Jan 2010 04:05:14 +0000 Received: (qmail 8632 invoked from network); 20 Jan 2010 04:04:52 -0000 Received: from unknown (76.252.112.72) by p3plsmtpa01-08.prod.phx3.secureserver.net (72.167.82.88) with ESMTP; 20 Jan 2010 04:04:52 -0000 Message-ID: <4B5680DA.3000600@rowe-clan.net> Date: Tue, 19 Jan 2010 22:04:42 -0600 From: "William A. Rowe Jr." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: dev@apr.apache.org Subject: Re: [Patch] RE: Windows drive letter check fails on lower case current working drive References: <000601ca98f9$44670000$cd350000$@qqmail.nl> In-Reply-To: <000601ca98f9$44670000$cd350000$@qqmail.nl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 1/19/2010 5:19 AM, Bert Huijben wrote: > Ping, > > This issue (and mailinglist thread) is now more than two months old. The latest patch adds a testcase showing the issue in the APR testsuite. (There is also an XFail test in the subversion testsuite for this issue) > > The patch was written on the 1.4.x branch but I svn switch'ed it to trunk for easy application. I'll commit/backport this right after tagging 1.4.2; presuming nobody notices any issues, this behavioral change will appear in 1.4.3. I'm still uncomfortable adding behavior-changing patches while we are attempting to pull off a regression-fix release, as you pointed out with respect to the hash/table flaw. So we can let 1.4.3 be a little more experimental and subject to a little extra scrutiny, while the users can put their hands already on 1.4.2 and resume using the most recent apr release with their svn package :)