Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3CEC0C52.6050807@ece.gatech.edu> Date: Wed, 22 May 2002 17:23:30 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Adding col to cygutils References: <20020522190201.71397.qmail@web20802.mail.yahoo.com> <20020522202228.GA19052@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Christopher Faylor wrote: [snip] > I guess past use is normally a good justification. However, it seems > like cygutils is a rather eclectic combination of utilities so basing > a decision to put something in cygutils based on what is already there > may not be a good plan. > > I do agree that this utility belongs in cygutils, fwiw. [snip] > >>>Well, of course. Why would you want to send a large attachment to the >>>thousands of people reading this list? >>> >>Because that is what is asked in the HOW-TO-CONTRIBUTE document that is >>part of cygutils. It asks to send a changelog as part of the message >>text, and a patch generated via "cvs diff" along with a tarball of new >>files to cygwin@cygwin.com. If that is no longer the case, then I will >>be glad to update the HOW-TO-CONTRIBUTE document to reflect the current >>policies regarding submissions. I would just need to know what they >>are first. >> > > I wasn't aware that the HOW-TO-CONTRIBUTE suggested sending a tar file > to the cygwin mailing list. That is a big no-no. Okay. I will revise the documentation. *after* discussion on the list about whether new program 'X' belongs in cygutils, THEN send the stuff to me... > Sending binaries here > should really be a last resort type of thing. There is no reason that > everyone on the list should be interested in seeing this type of file. True. > I guess I should go educate myself on the documentation that comes with > cygutils. > > Maybe a clearer statement of what makes a good cygutils package would be > nice. Why should a package be included in cygutils? IMO, it is because > it is a small (one or two c files) general-purpose program. The > justification that it is in the utils-linux package on Red Hat is a good > one, too. These are good ideas. I'll add some words to that effect in the documentation. --Chuck -- 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/