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 Message-ID: <1264BCF4F426D611B0B00050DA782A50014C2372@mail.gft.com> From: "Schaible, Jorg" To: cygwin AT cygwin DOT com Subject: RE: Adding col to cygutils Date: Thu, 23 May 2002 21:22:19 +0200 MIME-Version: 1.0 Content-Type: text/plain Hi Chuck, >I know this. However, right now I do not want to do that -- >not because > I'm a control freak or anything, but I just haven't figured out the >best way to handle commits from multiple developers (authorization, >approval (reversals?) etc). I'm usually pretty responsive to updates >and such (no complaints so far) and really, there are only three >contributors other than me -- there haven't really been a whole lot of >updates to deal with. > >I don't WANT cygutils to grow so large that we need multiple approved >committers and "community standards" and suchlike. For now, the three >people who this actually affects can continue to send me their >patches, >and I'll apply them. If my latency gets too large, or I hear >complaints >from those three poeple, then I'll re-evaluate... I thought there are already more submaintainers and with David the package is obviously growing. Basically I don't like very much posting diffs to my own utilities and keeping my own CVS developer repository. Additionally I supposed that your inbox is quite full enough with such kind of mails (regarding the number of Cygwin packages you're maintaining). But - as I said - it was just a proposal open for discussion. Finally these utilities are not THAT important anyway :) 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/