X-Spam-Check-By: sourceware.org X-SBRS: None X-IronPort-AV: i="4.09,252,1157353200"; d="scan'208"; a="150602578:sNHT18453162" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [ANNOUNCEMENT] Updated: bash-3.1-9 Date: Tue, 3 Oct 2006 17:03:26 -0700 Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5AC2C@SDGEXEVS02.corp.intuit.net> In-Reply-To: From: "Wilks, Dan" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k9403aZ2017750 Eric Blake wrote: > First, if a script is > specified with a DOS path instead of a POSIX path (although this is not > the recommended behavior in cygwin), bash will ensure that the underlying > mount mode is respected, rather than the default cygwin behavior of using > binary mode, allowing the use of DOS paths on text mounts the way 3.1-6 > behaved. Eric, as one of the complainers :) thanks. I just wanted to check in and say that our case of executing a cr/lf script via a DOS path on a text mount is working as well as it used to. -- 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/