Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Fri, 5 May 2000 20:28:21 -0400
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	cygwin-apps AT sourceware DOT cygnus DOT com
Message-ID:	<20000505202821.A19419@cygnus.com>
Reply-To:	cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To:	cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.1.12i

I've set up a new mailing list "cygwin-apps".  The purpose of this list
is to discuss porting issues for cygwin applications.

This would be a good place, for instance, for Earnie to post any future
patches for bash or ash.

(I hope that we won't need to have a cygwin-apps-patches.  That would
probably be overkill.)

I would like to keep this newsgroup more as a forum for discussing
solutions, and not as a place for generic bug-reporting "My bash broke.
You fix?" messages.  However, I'd like to see what develops before I
pass judgement.

-- 
cgf AT cygnus DOT com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

- Raw text -