Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
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:	patl AT cag DOT lcs DOT mit DOT edu (Patrick J. LoPresti)
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: Maintainers wanted
References:	<19991118160433 DOT A13395 AT cygnus DOT com>
Date:	19 Nov 1999 12:46:34 -0500
In-Reply-To:	Chris Faylor's message of "18 Nov 1999 16:04:54 -0500"
Message-ID:	<s5gyabu9xxh.fsf@egghead.curl.com>
Lines:	18
X-Mailer:	Gnus v5.6.27/Emacs 20.4

>>>>> "cgf" == Chris Faylor <cgf AT cygnus DOT com> writes:

 cgf> What I would like to do is break each of these up into its own
 cgf> tar file and then provide the maintainer with a way to upload
 cgf> updated tar files into an incoming area.

Wouldn't a CVS repository be superior in every respect to uploading
tarballs?  It would be more efficient for the maintainer, have a
revision history, make it easier for others to monitor and
contribute...

If Cygnus does not have the resources to host it, I believe the folks
at sourceforge.org would do it for free, at least for the open-source
bits (which everything but winsup is, right?).

Just a thought.

 - Pat

- Raw text -