From owner-freebsd-hackers Thu Jun 3 19:18:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 7327714C47 for ; Thu, 3 Jun 1999 19:18:49 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 3612 invoked from network); 4 Jun 1999 02:18:33 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 4 Jun 1999 02:18:33 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id VAA05115; Thu, 3 Jun 1999 21:18:27 -0500 (EST) From: "John S. Dyson" Message-Id: <199906040218.VAA05115@dyson.iquest.net> Subject: Re: 3.2-stable, panic #12 In-Reply-To: from Bill Fumerola at "Jun 3, 99 05:51:39 pm" To: billf@chc-chimes.com (Bill Fumerola) Date: Thu, 3 Jun 1999 21:18:26 -0500 (EST) Cc: brian@Awfulhak.org, dyson@iquest.net, ahasty@mindspring.com, dillon@apollo.backplane.com, crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG, schimken@cs.rpi.edu X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 4 Jun 1999, Brian Somers wrote: > > > The system was becoming unstable due to Matts changes. Whether the > > instabilities were in Matts code or somewhere else is irrelevent. > > The reaction was (IMHO) the right thing to do. > > I think where the problem lied is very relevent. > > If the problems are not his fault are you saying he should have backed > out his changes because they exposed old faulty code? What kind of > progress is that? > The key is that if problems are going to be uncovered, then understanding the rest of the code well enough to fix it is important. There were not only cases of new or uncovered bugs, but regression and mistaken removal of features that weren't understood. All of the stuff requires some kind of learning curve, and just jumping in and "coding" isn't really a wise thing to do or allow. IMO, revokation of commit privs has given enough time to support the learning curve and enforce a review process. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message