From owner-freebsd-current  Sun Feb 22 19:54:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA10789
          for freebsd-current-outgoing; Sun, 22 Feb 1998 19:54:57 -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 TAA10284
          for <current@FreeBSD.ORG>; Sun, 22 Feb 1998 19:52:35 -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 UAA15670;
	Sun, 22 Feb 1998 20:48:05 -0700 (MST)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id UAA26504; Sun, 22 Feb 1998 20:47:57 -0700
Date: Sun, 22 Feb 1998 20:47:57 -0700
Message-Id: <199802230347.UAA26504@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Brian Handy <handy@sag.space.lockheed.com>
Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Nate Williams <nate@mt.sri.com>,
        current@FreeBSD.ORG
Subject: Re: More breakage in -current as a result of header frobbing.
In-Reply-To: <Pine.OSF.3.96.980222163708.19637A-100000@sag.space.lockheed.com>
References: <Pine.BSF.3.96.980222174223.14406Y-100000@localhost>
	<Pine.OSF.3.96.980222163708.19637A-100000@sag.space.lockheed.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >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.

Exactly!  I'm not complaining about 'buggy/complex' software, but about
stupid silly bugs.  Things not building, include files not working in a
'build world', stuff that compiles but could never even run, etc...

Basicaly, simply Q&A stuff is what I'm complaining about, not highly
complex fixes to bugs that don't show up in simply Q&A testing.


Nate

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message