Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 8 Apr 2005 13:13:57 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: maintaining bash
Message-ID:	<20050408111357.GO1471@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<79F81D5F4790D344B05F489CE2AC8AB717CECB AT dubexdc03 DOT dubex DOT net>
Mime-Version:	1.0
In-Reply-To:	<79F81D5F4790D344B05F489CE2AC8AB717CECB@dubexdc03.dubex.net>
User-Agent:	Mutt/1.4.2i

On Apr  8 12:19, David Dindorp wrote:
> To be fair, this is probably more a Cygwin DLL problem than a bash
> problem, or perhaps a "bash hasn't kept up with changes in Cygwin
> because the maintainer haven't had the time" problem.  It's running
> quite stable under 1.5.10, it sucks with 1.5.12 and 1.5.13 and any
> of the latest snapshots..  (Haven't tried 1.5.11, but I will as soon
> as I get the time.)

It would be more helpful to test with 1.5.14 and current snapshots
and to help tracking down the problem in Cygwin you suspect.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/

- Raw text -