Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 23 May 2002 11:25:32 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Adding col to cygutils Message-ID: <20020523152532.GC4206@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1264BCF4F426D611B0B00050DA782A50014C234A AT mail DOT gft DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1264BCF4F426D611B0B00050DA782A50014C234A@mail.gft.com> User-Agent: Mutt/1.3.23.1i On Thu, May 23, 2002 at 12:39:32PM +0200, Schaible, Jorg wrote: > >>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. You're wrong. If Chuck wants to give people write access to cygwin-apps, we can accommodate him. cgf -- 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/