From owner-freebsd-current Fri Feb 20 18:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08367 for freebsd-current-outgoing; Fri, 20 Feb 1998 18:52:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08354 for ; Fri, 20 Feb 1998 18:52:36 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id SAA23065; Fri, 20 Feb 1998 18:51:55 -0800 (PST) To: John Birrell cc: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-reply-to: Your message of "Sat, 21 Feb 1998 13:45:02 +1100." <199802210245.NAA06439@cimlogic.com.au> Date: Fri, 20 Feb 1998 18:51:55 -0800 Message-ID: <23061.888029515@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan K. Hubbard wrote: > > Yeah, no kidding. Since nobody seems to be build testing their > > changes anymore I guess I'll just put this on the "indefinate > > postponement" list. > > Come on, it's not that bad. My build is nearly complete, so I'll > commit a fix to sys/time.h Yeah, but as Greg has already noted, it's been broken almost *every day* for the last week or so. If it's possible for it to be any worse, I'm not sure I want to know. :-) It's also annoying that all of these errors could have been found by a simple world build - something I thought we were supposed to do as part of committing; I've certainly gotten my ass chewed for not doing so in the past and thus feel more than justified in chewing on others for the same sin. In any case, thanks for committing a fix, anyway. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message