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: Sat, 9 Jul 2005 00:16:36 +0200 (MET DST)
From: Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To: Eric Blake <ericblake AT comcast DOT net>
cc: cygwin AT cygwin DOT com
Subject: Re: Problems with ash-20040127-3 (Attn: bash maintainer)
In-Reply-To: <070820052135.10000.42CEF188000C8AFE0000271022064246130A050E040D0C079D0A@comcast.net>
Message-ID: <Pine.OSF.4.21.0507090004590.14872-100000@ax0rm1.roma1.infn.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2005.7.8.28
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'



On Fri, 8 Jul 2005, Eric Blake wrote:

> ... 
> 
> Meanwhile, you will have to wait patiently until the upstream
> maintainer releases a patch (because I haven't the faintest clue
> where in the lexer to look for fixing his parse error).  Repeated
> pinging on the cygwin list will not help speed up the situation.
> 
> --
> Eric Blake
> volunteer cygwin bash maintainer
> 
> 
> 

My previous mail was only for the sake of completeness NOT to ping.

I have seen the '(Attn: bash maintainer)' only when that mail was started,
i.e. to late to correct the subject field.

angelo.


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