From owner-cvs-all Sat Dec 4 11: 1:43 1999 Delivered-To: cvs-all@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id F155A14CD4; Sat, 4 Dec 1999 11:01:37 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA23013; Sat, 4 Dec 1999 14:00:24 -0500 (EST) Date: Sat, 4 Dec 1999 14:00:24 -0500 (EST) From: "Matthew N. Dodd" To: Matthew Jacob Cc: Nick Hibma , cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern subr_bus.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Sat, 4 Dec 1999, Matthew Jacob wrote: > > This is a ridiculous proposition, you wanting me to spend about 500 to > > 1000 Euro, just to make your life easier. If you can't fix typo's when > > No, I want folks be competent and responsible integrators. And I'll > back this with over 20 years experience in this area. I don't think anyone is against clean tree build testing; its the expectation that everyone should have to come up with the hardware to do their own testing in a reasonable amount of time. I'd submit that a set of central systems able to handle patch-sets in a batch manner would satisfy eveyone if turnaround could be delivered in a reasonable amount of time (say 2 to 4 hours?). Does someone want to get handy with perl, formail, and procmail and create such a beast? I'm fairly sure that the cvs commit checker could verify that the checkin had an approved MD5 signature. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message