> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Jordan K. Hubbard
- Re: FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Jordan K. Hubbard
- Re: FreeBSD Build status Paul Richards
- Re: FreeBSD Build status Peter Jeremy
- Re: FreeBSD Build status Szilveszter Adam
- Re: FreeBSD Build status Jordan K. Hubbard
- Re: FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Anatoly Vorobey
- Re: FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Mike Nowlin
- Re: FreeBSD Build status Boris Popov
- Re: FreeBSD Build status Narvi
- Re: FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Narvi
- Re: FreeBSD Build status Poul-Henning Kamp
- Re: FreeBSD Build status Bill Fumerola