From owner-freebsd-current  Sun Feb 22 17:49:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA22017
          for freebsd-current-outgoing; Sun, 22 Feb 1998 17:49:45 -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 RAA22008
          for <current@FreeBSD.ORG>; Sun, 22 Feb 1998 17:49:43 -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 RAA29561; Sun, 22 Feb 1998 17:37:55 -0800 (PST)
To: Chuck Robey <chuckr@glue.umd.edu>
cc: Greg Lehey <grog@lemis.com>, Nate Williams <nate@mt.sri.com>,
        Terry Lambert <tlambert@primenet.com>, current@FreeBSD.ORG
Subject: Re: More breakage in -current as a result of header frobbing. 
In-reply-to: Your message of "Sun, 22 Feb 1998 17:50:31 EST."
             <Pine.BSF.3.96.980222174223.14406Y-100000@localhost> 
Date: Sun, 22 Feb 1998 17:37:54 -0800
Message-ID: <29557.888197874@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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

Gosh, why stop there?  Why don't we just put the developer in the
stocks and place them on display in the town square? :-)

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.

					Jordan

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