On Tue, 18 Apr 2000, Peter Jeremy wrote:
> On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote:
> >> As for the lists being tedious and long: I've sorted the content by
> >> relevance, and it was my hope that over time they would shrink to
> >> zero if we annoyed people enough with them.
> >
> >I think that's too much annoyance, really. I can see most people
> >simply unsubscribing from -current in the face of a mail that long and
> >tedious
>
> 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).
>
It *IS* a bad idea. Consider how big the failure report can be. Why not
instead:
1) have the report automatically uploaded on web
2) have the summary of summaries be sent to -current
The summary of summaries would roughly look like this:
Subject: -current build report
Success: world, generic
Fail: lint
For details, see http://blah.foo.bar/FreeBSD-build/date
It conveys the information most needed, and can hardly hurt anybody's
mailbox.
>
> Peter
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
