From owner-freebsd-current Mon Nov 13 17:34:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA10768 for current-outgoing; Mon, 13 Nov 1995 17:34:32 -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 RAA10762 for ; Mon, 13 Nov 1995 17:34:26 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id SAA01103; Mon, 13 Nov 1995 18:36:15 -0700 Date: Mon, 13 Nov 1995 18:36:15 -0700 From: Nate Williams Message-Id: <199511140136.SAA01103@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: <199511140126.UAA00419@crh.cl.msu.edu> References: <199511140125.SAA01060@rocky.sri.MT.net> <199511140126.UAA00419@crh.cl.msu.edu> Sender: owner-current@freebsd.org Precedence: bulk Charles Henrich writes: > > I think you underestimate the time needed to test something so critical > > as this. > > I find it hard to believe it would have taken longer than the 3 or 4 > months its been since he posted them. This assumes that the folks have *nothing* else to work on. There have been plenty of other 'show stopper' bugs in the 2.1 tree that have taken up lots of their time. Heck, I'll bet they could re-write the entire VM system from scratch in 3-4 months. :) > Even if there truly was no time to review the patches for 2.1 since > then, would it have not made sense to pull them into 2.2 to get the > ball rolling? 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. I've been bitten too many times by committing bad patches to the CVS tree that fix a 'critical' bug,when in fact the fix was worse than the original problem. :( Nate