From owner-freebsd-current Sat Feb 21 01:14:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23579 for freebsd-current-outgoing; Sat, 21 Feb 1998 01:14:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23545 for ; Sat, 21 Feb 1998 01:13:51 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id TAA00431; Sat, 21 Feb 1998 19:39:54 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802210839.TAA00431@cimlogic.com.au> Subject: Re: More breakage in -current as a result of header frobbing. In-Reply-To: <24223.888049047@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 21, 98 00:17:27 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 21 Feb 1998 19:39:53 +1100 (EST) Cc: grog@lemis.com, jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > 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. Forward it to -committers and let others deal with it. -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message