delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
Message-ID: | <4015B3ED.1060604@acm.org> |
Date: | Mon, 26 Jan 2004 16:42:21 -0800 |
From: | David Rothenberger <daveroth AT acm DOT org> |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: ash signal problems with latest CVS |
References: | <16405 DOT 41671 DOT 479106 DOT 886434 AT forbin DOT entomo DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0401261820070 DOT 11773 AT eos> |
In-Reply-To: | <Pine.GSO.4.58.0401261820070.11773@eos> |
X-IsSubscribed: | yes |
Brian Ford wrote: > Are you sure this is the latest CVS? It looks like the same problem fixed > here to me: > > http://www.cygwin.com/ml/cygwin/2004-01/msg01140.html Yes, I'm sure it is the latest CVS. The problem above is fixed in my build, but not the problem I reported. It looks the same, but the shells are different... Dave -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |