On Tue, Apr 18, 2000 at 03:25:35PM +1000, 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).

Sorry that I just chime in, but wouldn't it be more appropriate to go for a
system similar to the one at mozilla.org? They do pretty much the same
things that have been discussed here, but it looks so cooool... and does not
bother people on normal mailing lists. They have tinderbox.mozilla.org,
which always inidcates current build status on a number of machines (and
OS-es) the log is available too. And it is integrated with the CVS system so
you can see at once what commits have been made since the last build
attempt, etc. Maybe we could adapt this system to our needs? (they do not
bother about warnings, for example.)

Just my thoughts...

Szilveszter ADAM
Szeged University
Szeged Hungary

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to