From owner-freebsd-current Mon Nov 13 17:44:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA11240 for current-outgoing; Mon, 13 Nov 1995 17:44:24 -0800 Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA11234 for ; Mon, 13 Nov 1995 17:44:21 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id SAA01144; Mon, 13 Nov 1995 18:46:41 -0700 Date: Mon, 13 Nov 1995 18:46:41 -0700 From: Nate Williams Message-Id: <199511140146.SAA01144@rocky.sri.MT.net> To: Charles Henrich Cc: nate@rocky.sri.MT.net (Nate Williams), freebsd-current@freebsd.org Subject: Re: ISP state their FreeBSD concerns In-Reply-To: <199511140138.UAA00517@crh.cl.msu.edu> References: <199511140136.SAA01103@rocky.sri.MT.net> <199511140138.UAA00517@crh.cl.msu.edu> Sender: owner-current@freebsd.org Precedence: bulk > > I would never commit a patch that haven't been reviewed or at least > > tested on my own machines. Just because something 'looks like it > > solves' a problem doesn't mean it's a correct solution. It may simply > > hide the problem or move it to somewhere else. There is *nothing* worse > > than a poor fix. This is NOT to say that Matt's solution was poor, but > > until it is reviewed and tested it *shouldn't* go into the tree. > > Ack, I concur as well. What I meant was do a quick review instead of > a massive review for 2.2. Part of the problem I think is that Matt > doesnt have a track record here. I know (of) Matt from my Amiga days, > where he has done incredible amounts of work, including porting Unix > to the damn thing. He also had (is?) been running it on his heavily > loaded ISP company at the time if I'm not mistaken, lending it some > credibility. You have more information that the folks responsible for that part of the system. In any case, I'm going home now to watch football, and will shutup and not post anything else on this subject. In summary, I think the VM folks are doing a good job, and posting like 'Why didn't you do this, you had plenty of time' can sometimes come out wrong when you are the receiving end. This is a fun project, and the release folks are pretty stressed out right now. Wait until the release is out before pointing fingers at over-worked folks. :) Nate