From owner-freebsd-audit Mon Jun 18 12:17: 3 2001 Delivered-To: freebsd-audit@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B14CA37B403 for ; Mon, 18 Jun 2001 12:17:00 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA59054; Mon, 18 Jun 2001 15:16:54 -0400 (EDT) (envelope-from wollman) Date: Mon, 18 Jun 2001 15:16:54 -0400 (EDT) From: Garrett Wollman Message-Id: <200106181916.PAA59054@khavrinen.lcs.mit.edu> To: Dag-Erling Smorgrav Cc: audit@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/rarpd Makefile rarpd.8 rarpd.c In-Reply-To: References: <200106180648.f5I6mXw73601@freefall.freebsd.org> <74656.992853414@axl.seasidesoftware.co.za> <20010618092759.C9834@xor.obsecurity.org> Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > How about setting up a -review list for general code review, and > trying to keep -audit more or less focused on reviews and audits of > security-sensitive code? More unfocused mailing-lists are rarely helpful. Better to post requests for review where the knowledgeable (or affected) people are known to be hanging out. This might be on -net, -bugs, -current, -fs, or any number of other lists, depending on the nature of the change. In other words, it's reasonable to expect developers to be able to use their heads and think for a moment about who will be affected by a change. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message