Matthew Braithwaite wrote:
>
> I have a dedicated machine installed and firewalled, so I should get
> to this this weekend. If anybody has any particular features they
> want -- and in particular, any strong feelings about whether
> ``complain repeatedly until fixed'' or ``complain once when it breaks
> and then be silent until it's okay again'' is the right behavior --
> let me know.
>
> I am hesitant to e-mail the entire build log when the build fails,
> since this would be a very large message. Unfortunately, I'm on
> (intermittently connected) ISDN, so putting it on a web server here
> isn't too useful either. Sigh. In another project for which I'm
> doing this, mailing the last 100 lines of the build usually gives
> enough info.
I think the GCC project has it pretty much right now.
It emails everyone who checked something in since the
last time it knew that it was working, with only the
first email suggesting responsibility :-). After that,
the messages are "You should be aware..." messages.
I think Michael Messner does it, if I remember correctly.
It has been a while since I got one....
Received on Sat Oct 21 14:36:13 2006