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
Date: Mon, 6 Mar 2000 15:26:27 -0500
Message-Id: <200003062026.PAA06971@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000306144552.A15739@cygnus.com> (message from Chris Faylor on
	Mon, 6 Mar 2000 14:45:52 -0500)
Subject: Re: Changing cygwin-developers "charter"?
References:  <20000306144552 DOT A15739 AT cygnus DOT com>


Note that the DJGPP 'workers' list includes talk about porting
"standard" programs (i.e. the usual GNU stuff) to DJGPP, but other
porting topics go to the regular list.  Mostly, it's defined by the
people - if one of the djgpp people happens to be porting a program
and runs into a problem, there's a good chance that it really is a
djgpp issue, but if J Random User off the user's list is porting a
program and runs into a problem, it's more likely to be a generic
problem.