From owner-cvs-all@FreeBSD.ORG  Wed Jan 21 13:16:51 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6595A16A4CE
	for <cvs-all@FreeBSD.org>; Wed, 21 Jan 2004 13:16:51 -0800 (PST)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id BE04743D53
	for <cvs-all@FreeBSD.org>; Wed, 21 Jan 2004 13:16:47 -0800 (PST)
	(envelope-from nate@root.org)
Received: (qmail 4000 invoked by uid 1000); 21 Jan 2004 21:16:48 -0000
Date: Wed, 21 Jan 2004 13:16:48 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: Mike Silbersack <silby@silby.com>
In-Reply-To: <20040121140858.W528@odysseus.silby.com>
Message-ID: <20040121131001.P3938@root.org>
References: <200401210150.i0L1oSmg073908@repoman.freebsd.org>   
	<20040121015059.D56100@odysseus.silby.com>
	<20040121140858.W528@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
cc: Colin Percival <colin.percival@wadham.ox.ac.uk>
Subject: Re: cvs commit: CVSROOT access
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jan 2004 21:16:51 -0000

On Wed, 21 Jan 2004, Mike Silbersack wrote:
> On Wed, 21 Jan 2004, Nate Lawson wrote:
> > Can I commit that to fortune(6)?
> >
> > -Nate
>
> Fine with me.  I think you should also add Colin's subsequent posting to
> -current about lines of code to the mix... he's waaaay too excited.

It was a joke about eager committers.  I've come to dread committing.  :)

> Hint to colin:  It's not botching commits that makes having a commit bit
> bad.  The real torture is when you stumble across a piece of broken code
> and think "Gee, it'd be nice if someone would fix this so I can get what I
> was working on done."
>
> Very shortly after that, you will realize that *you* have to fix the
> broken code, and that your pet project upon which depends upon this broken
> code will have to be put on the back burner.

Muagh! (expression of intense dismay).  I'm in the middle of that right
now as CPUs need to gain newbus attachments for my cpufreq driver.  And I
was just dragged through it finding all the ways APIC ids, ACPI Processor
ids, and PCPU ids can all not line up.

Actually, working on ACPI has become an exercise in how deep on the stack
I can recurse.  I think it started somewhere when I was working on CAM and
my laptop wouldn't suspend correctly and I thought "hmm, let's figure out
why".

-Nate