From owner-freebsd-current Tue Apr 18 0:48:35 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 E32C637BA34 for ; Tue, 18 Apr 2000 00:48:30 -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 JAA14872; Tue, 18 Apr 2000 09:48:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Narvi Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Tue, 18 Apr 2000 09:44:32 +0200." Date: Tue, 18 Apr 2000 09:48:11 +0200 Message-ID: <14870.956044091@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nar vi writes: >> >The summary of summaries would roughly look like this: >> > >> > Subject: -current build report >> > >> > Success: world, generic >> > Fail: lint >> >> The First part of the email is a summary just like that. >> > >See what Boris Popov writes on the issue. I am sure there are more people >who think that a big status report is not cost effective, if they can get >a *short* summary, and an url where they can get the full report. Listen, we are talking about an email which is shorter than the list of open PRs, and if people actually *DO* something about it it will get shorter fast The only reason it is a long report right now is that people are sloppy! -- 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