Date: Tue, 18 Apr 2000 08:26:01 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Peter Jeremy <peter.jeremy@alcatel.com.au> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <14259.956039161@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 18 Apr 2000 15:25:35 %2B1000." <00Apr18.152537est.115213@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <00Apr18.152537est.115213@border.alcanet.com.au>, Peter Jeremy write s: >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? All the MUA's I've ever used allowed me to delete a mail >before reading all of it, so I don't see that having detailed >information (at the end) is a real issue (though it might be for >someove paying by the byte). I agree. >Comments: >- I hope it has a well-defined subject so it can be easily recognized. "FreeBSD Build status" >- I presume it's built using the default make.conf. Yes. >- It would be nice if it reported changes since the previous day (or > successful build). This would make it easier to see what has been > broken recently. Well, it reports on sundays and if anything doesn't build. If it reports, it includes the errors which from the non-building components and "New warnings in *" delta lists relative to the previous report. I've sorted the report so that the most interesting things are at the top. Other ideas welcome. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14259.956039161>