X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: [ANNOUNCEMENT] Updated: bash-3.1-9 Date: Tue, 3 Oct 2006 16:28:13 +0000 (UTC) Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 mwoehlke tibco.com> writes: > > Eric Blake wrote: > > Second, this release adds a new shopt, igncr, which dynamically > > tells bash to ignore all \r in the input file when it is set; however, it > > defaults to unset. > > So, I keep wanting to know if you are thinking about submitting this > upstream (or have you done so already?)... > I'm hoping to port the patches to the 3.2 beta before proposing them upstream (right now, my cygwin TODO list includes: get coreutils 6.3 stable ported to cygwin, get bash 3.2beta ported to cygwin as experimental, post bash patches upstream, update bash-completion to use cygport and add some long overdue promised completion functions for cygwin). As written, my patch is conditionalized on __CYGWIN__, but when proposing it upstream, I will try to make it more generic. -- Eric Blake -- 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/