From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 28 07:10:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D16237B401 for ; Sat, 28 Jun 2003 07:10:10 -0700 (PDT) Received: from sark.cc.gatech.edu (sark.cc.gatech.edu [130.207.7.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6FD743F75 for ; Sat, 28 Jun 2003 07:10:09 -0700 (PDT) (envelope-from insanc@cc.gatech.edu) Received: from myrna.cc.gatech.edu (myrna.cc.gatech.edu [130.207.107.16]) by sark.cc.gatech.edu (8.12.9/8.12.8) with ESMTP id h5SEA812023420 for ; Sat, 28 Jun 2003 10:10:08 -0400 (EDT) Received: (from insanc@localhost) by myrna.cc.gatech.edu (8.12.9/8.12.8) id h5SEA8GX027952 for freebsd-hackers@freebsd.org; Sat, 28 Jun 2003 10:10:08 -0400 Date: Sat, 28 Jun 2003 10:10:08 -0400 From: Joseph Holland King To: freebsd-hackers@freebsd.org Message-ID: <20030628101008.A27124@myrna.cc.gatech.edu> References: <20030627231013.GA41033@webserver.get-linux.org> <20030627231805.GB410@nitro.dk> <3EFD4AF6.F8F471D6@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EFD4AF6.F8F471D6@mindspring.com>; from tlambert2@mindspring.com on Sat, Jun 28, 2003 at 12:59:50AM -0700 Subject: Re: TODO list? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2003 14:10:10 -0000 On Sat, Jun 28, 2003 at 12:59:50AM -0700, Terry Lambert had the gall to say: > Give him a commit bit, and he can quickly grind through all the > PR's that already have diff's attached to them, and have just sat > there forever. All he'd need to do was verify that there was a > problem that was being fixed, and the code didn't look like it > would cause damage. If it ends up causing damage anyway, the fix > can always be backed out later. Making send-pr actually result in > code changes would probably be the most valuable thing anyone could > do for the project, and it would give him a chance to read and to > understand a lot of diverse code, in the process, to get up to speed > on writing his own fixes for PR's without fixes attached. heh, i must say that without a commit bit its almost impossible to get any of the pr's closed, even ones that are five years old with a fix attached. -- Joseph Holland King gte743n@mail.gatech.edu