This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding col to cygutils


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]