X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 1 Jul 2009 23:16:25 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] [1.7] Updated [security]: bash-3.2.49-23 Message-ID: <20090702031625.GA23085@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <55392.99.237.216.211.1246503158.squirrel@www.sidefx.com> <4A4C238B.8070804@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A4C238B.8070804@byu.net> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: 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 Wed, Jul 01, 2009 at 09:03:39PM -0600, Eric Blake wrote: >If you have /cygdrive/c mounted as a text mount point, then > >echo > /cygdrive/c/file > >continues to do text processing, but the alternate construct > >echo > c:\file > >now behaves in a binary fashion (in 1.5, I had been special casing DOS >paths to make them obey the underlying mount point, but cygwin 1.7 goes >further to discourage DOS paths, so I'm no longer worried about >maintaining that special-case). And for those who want to wail about this, take a look at the various "Why is Cygwin so slow????" threads that have been here in the last month. Every special case accommodation we make to allow MS-DOSisms to work seamlessly adds code to Cygwin and cause corresponding slowness for everything. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple