From owner-freebsd-current Mon Apr 17 23:39:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B864F37BC0D for ; Mon, 17 Apr 2000 23:39:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA14396; Tue, 18 Apr 2000 08:38:47 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 23:21:24 PDT." <3956.956038884@zippy.cdrom.com> Date: Tue, 18 Apr 2000 08:38:47 +0200 Message-ID: <14394.956039927@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3956.956038884@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> 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. Because the people who don't compile LINT are unlikely to subscribe to it. The alternative is to send it to committers, but I pressume all the ports people would be pretty annoyed, and by sending it to -current maybe a new junior hacker or two could be ferret out :-) >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. That makes sense. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message