Date: Wed, 21 Jan 2004 13:16:48 -0800 (PST) From: Nate Lawson <nate@root.org> To: Mike Silbersack <silby@silby.com> Cc: Colin Percival <colin.percival@wadham.ox.ac.uk> Subject: Re: cvs commit: CVSROOT access Message-ID: <20040121131001.P3938@root.org> In-Reply-To: <20040121140858.W528@odysseus.silby.com> References: <200401210150.i0L1oSmg073908@repoman.freebsd.org> <20040121015059.D56100@odysseus.silby.com> <20040121140858.W528@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040121131001.P3938>