From owner-freebsd-current  Sat Feb 21 00:36:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA18250
          for freebsd-current-outgoing; Sat, 21 Feb 1998 00:36:53 -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 AAA18245
          for <current@freebsd.org>; Sat, 21 Feb 1998 00:36:51 -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 AAA24228; Sat, 21 Feb 1998 00:17:27 -0800 (PST)
To: Greg Lehey <grog@lemis.com>
cc: John Birrell <jb@cimlogic.com.au>, current@FreeBSD.ORG
Subject: Re: More breakage in -current as a result of header frobbing. 
In-reply-to: Your message of "Sat, 21 Feb 1998 14:38:03 +1030."
             <19980221143803.31160@freebie.lemis.com> 
Date: Sat, 21 Feb 1998 00:17:27 -0800
Message-ID: <24223.888049047@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Maybe now's an appropriate time to come out with a thing that I've
> been meaning to propose for some time:

Another possiblity is that I can have the messages which
current.freebsd.org sends me every time the 3.0 or 2.2 trees can't
have a release build made from them sent to a wider audience?
Having something tell you in 24 hours or less every time the
tree is broken is a powerful tool for letting you know it
needs fixing.

					Jordan

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