From owner-cvs-all  Tue Oct  3 20:19:55 2000
Delivered-To: cvs-all@freebsd.org
Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167])
	by hub.freebsd.org (Postfix) with ESMTP
	id B0FE637B66C; Tue,  3 Oct 2000 20:19:50 -0700 (PDT)
Received: by puck.firepipe.net (Postfix, from userid 1000)
	id AA5C11953; Tue,  3 Oct 2000 22:20:04 -0500 (EST)
Date: Tue, 3 Oct 2000 22:20:04 -0500
From: Will Andrews <will@physics.purdue.edu>
To: Paul Richards <paul@originative.co.uk>
Cc: Jordan Hubbard <jkh@winston.osd.bsdi.com>,
	Christopher Masto <chris@netmonger.net>,
	Warner Losh <imp@village.org>, Kris Kennaway <kris@FreeBSD.org>,
	Joseph Scott <joseph.scott@owp.csus.edu>,
	Brian Somers <brian@FreeBSD.org>, cvs-committers@FreeBSD.org,
	cvs-all@FreeBSD.org, freebsd-security@FreeBSD.org
Subject: Re: cvs commit: src/usr.bin/finger finger.c
Message-ID: <20001003222004.Z41798@puck.firepipe.net>
Reply-To: Will Andrews <will@physics.purdue.edu>
Mail-Followup-To: Will Andrews <will@physics.purdue.edu>,
	Paul Richards <paul@originative.co.uk>,
	Jordan Hubbard <jkh@winston.osd.bsdi.com>,
	Christopher Masto <chris@netmonger.net>,
	Warner Losh <imp@village.org>, Kris Kennaway <kris@FreeBSD.org>,
	Joseph Scott <joseph.scott@owp.csus.edu>,
	Brian Somers <brian@FreeBSD.org>, cvs-committers@FreeBSD.org,
	cvs-all@FreeBSD.org, freebsd-security@FreeBSD.org
References: <83262.970607906@winston.osd.bsdi.com> <39DA6055.594B13E4@originative.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <39DA6055.594B13E4@originative.co.uk>; from paul@originative.co.uk on Tue, Oct 03, 2000 at 11:40:21PM +0100
X-Operating-System: FreeBSD 4.1-STABLE i386
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Oct 03, 2000 at 11:40:21PM +0100, Paul Richards wrote:
> I think you're looking at it the wrong way around. The stable team
> wouldn't be putting in a lot of hours reviewing stable commits. Stable
> commits would only occur if the stable team did them i.e. no-one else
> would be allowed to commit to stable. The stable team would then monitor
> -current, noting commits that are bug fixes, and slating them for a MFC
> at a later date when it's felt they've had enough of a shakeout.

Uhm, I doubt you can come up with a comprehensive team of people who can
figure out the implications of X, Y, or Z to MFC.  This is a large
project, and everyone has different skills/knowledge about different
things.

Sorry, but no go on this.  I still think every committer should have a
couple other eyes lint their work.

-- 
Will Andrews <will@physics.purdue.edu> - Physics Computer Network wench
The Universal Answer to All Problems - "It has something to do with physics."
	-- Comic on door of Room 240, Physics Building, Purdue University


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message