Date: Fri, 20 Feb 1998 19:06:27 -0800 (PST) From: Sean Eric Fagan <sef@kithrup.com> To: current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Message-ID: <199802210306.TAA07907@kithrup.com> In-Reply-To: <23061.888029515.kithrup.freebsd.current@time.cdrom.com> References: Your message of "Sat, 21 Feb 1998 13:45:02 %2B1100." <199802210245.NAA06439@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <23061.888029515.kithrup.freebsd.current@time.cdrom.com> Jordan writes: >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. Interestingly enough, the same thing happens at my day job. In one case, we had no working build for two weeks because a single person didn't do a build test before checking in changes, and then, for the next 9 work days, checked in hacked "fixes" that also hadn't been tested. Given that a "make world" takes 1h50m on my K6 (as opposed to 17 hours on the machines at work), there isn't a whole lot of excuse to do it. Heck, I'm testing *my* pending changes by compiling on a 486DX-33 -- and that takes 21 hours. Remember: the onslaught of <$1k machines means cheap build machines for everyone ;). (And, hey, they're also predictin < $500 machines soon!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802210306.TAA07907>