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:	<1264BCF4F426D611B0B00050DA782A50014C234A@mail.gft.com>
From:	"Schaible, Jorg" <Joerg DOT Schaible AT gft DOT com>
To:	cygwin AT cygwin DOT com
Subject:	RE: Adding col to cygutils
Date:	Thu, 23 May 2002 12:39:32 +0200
MIME-Version:	1.0

>From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au]
>> From: Schaible, Jorg [mailto:Joerg DOT Schaible AT gft DOT com] 
>> Hi Chuck,
>> 
>> what about setting up a SourceForge project for cygutils ? 
>> Then every author or maintainer of his  small 'tool' may 
>> maintain and add stuff much more easily. 
>
>Sourceforge is no easier than cygwin-apps. They both use CVS.

Assuming that cygutils is a collection of very small, but maintained
utilities from various authors, it might be good if anyone of the authors
has also the right to change their (possibly) own code! Basically I do not
care where the CVS lives, but I assume also, that not all of these people
are write access granted in cygwin-apps (or at least for "their" files).
With SF Chuck could give each of the authors write access for the cygutils
package only and use defined (labeled) snapshots for the distribution.

Correct me if I am wrong.

Regards,
Jorg

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -