From owner-freebsd-current Sun Feb 22 16:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14162 for freebsd-current-outgoing; Sun, 22 Feb 1998 16:51:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA14157 for ; Sun, 22 Feb 1998 16:51:22 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA14142; Sun, 22 Feb 1998 16:41:47 -0800 Date: Sun, 22 Feb 1998 16:41:47 -0800 (PST) From: Brian Handy To: Chuck Robey Cc: Greg Lehey , "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Chuck writes:] >I think Jordan and Greg both have points they are correct about. What >about making a web page that the offender gets put on ... nothing >incredibly horrible, just a rogues gallery (I broke current on 00/00/00 >with a commit to " ... ". [Followed up with John Dyson as an example] People are confusing some issues here, and Terry pointed this out to me. Chuck is wrong, because John in fact does *not* often break the tree. His stuff makes it unstable and crash, but that's not the problem here. The problem here is people committing stuff that won't even *compile*. Hello? Everyone on the same thread yet? The problem here is getting the tree to just *compile*. We'll worry about it actually *working* later! You can't jump to an unstable -current until you can compile it! Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message