From owner-freebsd-audit Tue Dec 5 19:53:48 2000 From owner-freebsd-audit@FreeBSD.ORG Tue Dec 5 19:53:47 2000 Return-Path: Delivered-To: freebsd-audit@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 6EAEA37B400 for ; Tue, 5 Dec 2000 19:53:46 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id TAA09570; Tue, 5 Dec 2000 19:55:02 -0800 Date: Tue, 5 Dec 2000 19:55:02 -0800 From: kris@citusc.usc.edu To: Will Andrews Cc: audit@FreeBSD.ORG Subject: Re: audit code being submitted lately.. Message-ID: <20001205195502.A9566@citusc.usc.edu> References: <20001205221546.C575@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20001205221546.C575@puck.firepipe.net> Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 05, 2000 at 10:15:46PM -0500, Will Andrews wrote: > Hi all, > > I'm curious, at what point will all this audited code get committed? It > needs to settle in -current for awhile. > > I'd say commit it all to -current and see how things go. At this stage most of the patches are at the stage of "proposed patches" and need to be audited by at least one other person to make sure they a) actually fix problems, b) don't miss anything, and c) don't break things. The more complex the patches the more people should ideally be auditing them..usually with my patches I feel comfortable committing them if at least 2 people whose skills I trust give the ok. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message