From owner-freebsd-current Mon Aug 28 10:41: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FAE837B42C for ; Mon, 28 Aug 2000 10:41:02 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA23368; Mon, 28 Aug 2000 10:40:56 -0700 Date: Mon, 28 Aug 2000 10:37:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Mike Meyer , Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <200008281737.LAA02697@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Matthew Jacob writes: > : > I do read cvs-all, and I missed it. Not did I find device.hints in the > : > relevant Makefiles. Can you provide a pointer to details on how > : > /boot/device.hints is used in the build process, or how having an > : > empty one keeps you from shooting yourself in the foot? > : > : cvs-all is not appropriate. I am noticing a 3-7 day lag on UPDATING. > : Bad. > > cvs-all *IS*REQUIRED* for all people running -current. UPDATING tries > to cull things from there on an as needed basis. It is a service that > gets done when I have time. If someone wants to pay me a stipend to > drop everything the instant something is committed to the tree and > update UPDATING, then the lag will improve. Otherwise, 3-7 days > really isn't that bad and will continue to be the case. > > Warner Oops- I realize that what I said might have been construed as criticism- not meant at all! What I meant is that while cvs-all can be read by everyone, it's not always obvious from the flood of mail there, or if you're not a developer, what needs to change. In my opinion, people making major changes that require something in UPDATING, should coordinate with you *before* the commit. Only 5 or 6 brain cells are needed for this- I sure wish some of my fellow committers weren't such skinflints in this area. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message