Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Mon, 20 Jan 2003 22:18:44 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: True case-sensitive filenames Message-ID: <20030121031844.GA4209@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <59A835EDCDDBEB46BC75402F4604D55231AE32 AT elmer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59A835EDCDDBEB46BC75402F4604D55231AE32@elmer> User-Agent: Mutt/1.5.1i On Mon, Jan 20, 2003 at 03:36:14PM -0500, Sergey Okhapkin wrote: >Hmmm... Looks like hardlink method should work... > >The second argument why my patch was not accepted by cygwin maintainer >Geof Noer a while ago was that the customers who bought cygwin support >often use windows tools to create and edit files (like notepad) and >mixed case filenames may fool them. Chris, is it still an issue? Sure. I think I may have been the one who ultimately vetoed this idea. It just seemed like it was really prone to causing massive user confusion for, IMO, little gain. I was following this discussion to see if eventually there would be new ground covered but so far it seems to be treading on old familiar territory. If you have to really stand on your head to do simple things like renaming a file it really makes me think that this is not going to be a robust solution. cgf