X-Spam-Check-By: sourceware.org Date: Thu, 17 Aug 2006 16:25:10 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Cc: Eli Zaretskii Subject: Re: change in behavior of make from 3.80 to 3.81 Message-ID: <20060817142510.GH20467@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, Eli Zaretskii References: <01b901c6c116$21259430$a501a8c0@CAM.ARTIMI.COM> <6.2.3.4.2.20060816091525.0ab90af0@pop.nycap.rr.com> <20060816144110.GX20467@calimero.vinschen.de> <6.2.3.4.2.20060816111421.0b446b60@pop.nycap.rr.com> <20060816155054.GY20467@calimero.vinschen.de> <6.2.3.4.2.20060816144036.09695af0@pop.nycap.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Aug 17 09:59, Igor Peshansky wrote: > Actually, as Gareth mentioned, *Cygwin* allows colons in file names on > managed mounts. So, at the very least there'd be confusion of whether > c:\\TEMP is a directory TEMP in the root of the C: drive, or a file named > 'c:\\TEMP' in the current directory on a managed mount... Since colons are perfectly valid characters on POSIX file systems, there's no reason to generate a special case for Cygwin. The problems generated by using such filenames are identical on all these OSes. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/