delorie.com/archives/browse.cgi | search |
Message-Id: | <200003062004.PAA06753@delorie.com> |
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: | "Parker, Ron" <rdparker AT butlermfg DOT org> |
To: | cygwin-developers AT sourceware DOT cygnus DOT com |
Subject: | RE: Changing cygwin-developers "charter"? |
Date: | Mon, 6 Mar 2000 14:00:40 -0600 |
MIME-Version: | 1.0 |
X-Mailer: | Internet Mail Service (5.5.2448.0) |
I for one would like to keep this list as clean as possible. BTW, I didn't realize the Net Release discussion was outside the charter of this list. I thought discussing the next public release of cygwin1.dll and its associated packages was well within the discussion of cygwin development. After all development is often followed by distribution. (At least if the development is successful.) :) How about a cygwin-ports list? It could possibly replace the cygwin-xfree list.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |