From owner-freebsd-current@FreeBSD.ORG Wed Jan 14 19:06:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FF8B16A4CE for ; Wed, 14 Jan 2004 19:06:56 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A950643D1D for ; Wed, 14 Jan 2004 19:06:54 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com ([192.168.42.24]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i0F36r6T011548; Wed, 14 Jan 2004 21:06:53 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <400603B5.5050003@centtech.com> Date: Wed, 14 Jan 2004 21:06:29 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20040113093903.GA84055@mimoza.pantel.net> <1073998390.18384.19.camel@kaiser.sig11.org> <20040114001137.5ce8983b@piglet.goo> <1074000332.18384.43.camel@kaiser.sig11.org> <20040114003443.260c6738@piglet.goo> <4003F684.6090907@centtech.com> <20040115024919.GA50163@xor.obsecurity.org> In-Reply-To: <20040115024919.GA50163@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2004 03:06:56 -0000 Kris Kennaway wrote: >On Tue, Jan 13, 2004 at 07:45:40AM -0600, Eric Anderson wrote: > > > >>The NDIS thing is a great example.. I broke my kernel build when it was >>first going in, and I didn't even have a clue it was being worked on.. >>Had it not broken a few builds around the -current waterhole, I think it >>may have gone somewhat unnoticed (which would be too bad since it is a >>nice addition). >> >> > >You must have missed the email from the committer to current@ >detailing what the new code was and how it works. > > Actually, you are correct. I had a busted kernel, until I figured out what was wrong, and made my way past it. I sent some mails in that time, but didn't get to read any until my kernel was fixed - his mail went out after the cvs commits, and I was in between :).. However, I most likely missed an email or two in there anyway.. No worries - that was just the first example that came to my mind.. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. ------------------------------------------------------------------