From owner-freebsd-current Sun Feb 22 19:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09072 for freebsd-current-outgoing; Sun, 22 Feb 1998 19:47:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09061 for ; Sun, 22 Feb 1998 19:46:49 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA15571; Sun, 22 Feb 1998 20:39:43 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA26400; Sun, 22 Feb 1998 20:37:11 -0700 Date: Sun, 22 Feb 1998 20:37:11 -0700 Message-Id: <199802230337.UAA26400@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <29557.888197874@time.cdrom.com> References: <29557.888197874@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've not yet heard a proposed cure that wasn't worse than the disease > and would suggest that we all just Try A Little Harder rather than > instituting unworkable policies to a problem that simply requires a > bit more SELF CONTROL on the part of the developers to fix. What happens when the developers aren't showing any self control, like now? Then we have the problems we have now. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message