From owner-freebsd-current  Sat Feb 21 01:01:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA21225
          for freebsd-current-outgoing; Sat, 21 Feb 1998 01:01:24 -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 BAA21216
          for <current@FreeBSD.ORG>; Sat, 21 Feb 1998 01:01:21 -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 AAA25981; Sat, 21 Feb 1998 00:59:32 -0800 (PST)
To: Eivind Eklund <eivind@yes.no>
cc: Greg Lehey <grog@lemis.com>, 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 09:51:16 +0100."
             <19980221095116.15674@follo.net> 
Date: Sat, 21 Feb 1998 00:59:31 -0800
Message-ID: <25977.888051571@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Please send these to -stable/-current.  I'd also expect these to be
> much more reliable than the human reports, so it would be a good thing
> for all concerned.

Hmmm.  OK, let me figure out how to massage them into something more
human-readable (read: concise) and I'll give that some serious
thought.  Barring this, I might have something just sent to
-committers since they're the only ones who can do anything about it
anyway. ;)

				Jordan

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