From owner-freebsd-current  Mon Apr 17 23:19:57 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 6E18E37B64F
	for <current@FreeBSD.ORG>; Mon, 17 Apr 2000 23:19:53 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA03959;
	Mon, 17 Apr 2000 23:21:24 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Peter Jeremy <peter.jeremy@alcatel.com.au>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, current@FreeBSD.ORG
Subject: Re: FreeBSD Build status 
In-reply-to: Your message of "Tue, 18 Apr 2000 15:25:35 +1000."
             <00Apr18.152537est.115213@border.alcanet.com.au> 
Date: Mon, 17 Apr 2000 23:21:24 -0700
Message-ID: <3956.956038884@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> IMHO, it's not such a bad idea.  freebsd-current _is_ the place to
> report problems with -current, why can't the report be produced by a
> daemon?

Becuase it's chunky and regular enough that I don't see why we
also can't just create a new notification service for it.

Think a bit bigger-picture also; theoretically, we should have these
reports for -current and the RELENG_3 and RELENG_4 branches.  The
machine-resources are available for it, we just haven't organized
it properly.

- Jordan


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