From owner-cvs-all Fri Aug 28 18:03:52 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19062 for cvs-all-outgoing; Fri, 28 Aug 1998 18:03:52 -0700 (PDT) (envelope-from owner-cvs-all) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19055 for ; Fri, 28 Aug 1998 18:03:49 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id RAA20957; Fri, 28 Aug 1998 17:58:47 -0700 (PDT) Date: Fri, 28 Aug 1998 17:58:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199808290058.RAA20957@apollo.backplane.com> To: Poul-Henning Kamp Cc: John Polstra , committers@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: make.conf Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk :Matt, : :I'm one of those purists, and I would really appreciate if you would :try to understand that having commit-bit doesn't allow you to implement :"How the world should be according to >ME<" without the consensus of :the committers group in general and -core in particular. : :There are good choices and bad choices, rectifying the bad ones may :not be as trivial as they look. In general if they were they would :have been fixed by now. : :Please do understand that this is not just your sandbox, there are :a few hundred thousand people besides you who have to fit in this :sandbox. : :Widen your perspective a bit... My problem isn't with it being MY fix, my problem is with it taking dozens of emails arguing back and forth over something that ought to be a trivial problem to fix. We get into extreme arguments over a one line add in sys.mk that doesn't hurt *anyone* and adds a significant benefit (the 'feature', not the exact implementation of it). If you read over my original commits and original emails in regards to both ping and make.conf, you will find them to be quite amiable... I had no proble removing the -c portion of the ping commit. I have no problem discussing the make.conf localization issue that I would like to add to-current... an issue, I might add that, that isn't something I thought up in 10 seconds and decided to commit. We've been working with make.conf for well over 2 years and the relatively innocuous feature request and commit came out of those 2 years in working with it. Before you start accusing ME of trying to make the sandbox my own, review those emails and tell me whos the one whos acting like a bitch. It sure as hell isn't me! I'm trying to be reasable. I'm trying to build a concesus. All the hell I`m getting back from half the people responding to my emails and the thread in general are 'thou shalt not' or 'this is stupid', and various other insundry implications that I'm not worthy of being on the list, of making commits, or even making suggestions for gods sakes! I AM NOT A FUCKING 10 YEAR OLD! Don't expect me to meekly accept degrading emails, 'cause it isn't going to happen. I've worked with plenty of large groups and I have to say that my experience working with this one, so far, has been a severe mix. -Matt :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal : : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications (Please include original email in any response)