X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <55392.99.237.216.211.1246503158.squirrel@www.sidefx.com> In-Reply-To: References: Date: Wed, 1 Jul 2009 22:52:38 -0400 (EDT) Subject: Re: [ANNOUNCEMENT] [1.7] Updated [security]: bash-3.2.49-23 From: "Edward Lam" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, July 1, 2009 22:17, Eric Blake wrote: > It also removes special > handling for DOS paths, since cygwin 1.7 is less accommodating to those > (use /cygdrive instead). Can you clarify what this means exactly compared to say the latest bash version in cigwin 1.5? Personally, I rely on using DOS paths from the bash command line everyday. eg. "cd $FOO" where FOO is some environment variable containing a forward slash DOS path. -Edward -- 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