Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 3 Jan 2005 12:09:45 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: check_case:adjust still an option? Message-ID: <20050103110945.GE12820@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050102203221 DOT GB344 AT efn DOT org> <20050102213301 DOT GA552397 AT hpn5170> <20050102221844 DOT GA608 AT efn DOT org> <20050102231344 DOT GA35436409 AT hpn5170> <20050103011210 DOT GA2112 AT efn DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jan 2 20:21, Igor Pechtchanski wrote: > On Sun, 2 Jan 2005, Yitzchak Scott-Thoennes wrote: > > Seems kind of pointless, really. > > It is pointless. As I understood the documentation previously, it's the > POSIX path that should have been adjusted. As is, though, it's useless. > FWIW, I have nothing against removing the check_case:adjust logic, as long > as the check_case:strict one is left in-place. Unfortunately, most of the > check_case logic is associated with check_case:strict. I'd rather see check_case go away entirely since it's pointless entirely. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/