Date: Mon, 18 Jun 2001 15:16:54 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Dag-Erling Smorgrav <des@ofug.org> Cc: audit@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/rarpd Makefile rarpd.8 rarpd.c Message-ID: <200106181916.PAA59054@khavrinen.lcs.mit.edu> In-Reply-To: <xzpzob57i3c.fsf@flood.ping.uio.no> References: <200106180648.f5I6mXw73601@freefall.freebsd.org> <74656.992853414@axl.seasidesoftware.co.za> <20010618092759.C9834@xor.obsecurity.org> <xzpzob57i3c.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On 18 Jun 2001 20:34:15 +0200, Dag-Erling Smorgrav <des@ofug.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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106181916.PAA59054>