Fw: [GUMP] how to point the finger?

[Nicola Ken Barozzi <ni...@apache.org>]

----- Original Message -----
From: "Ovidiu Predescu" <ov...@cup.hp.com>
To: "Sam Ruby" <ru...@us.ibm.com>
Cc: <co...@jakarta.apache.org>
Sent: Wednesday, May 01, 2002 7:54 PM
Subject: [GUMP] how to point the finger?


> Sam,
>
> The GCC project uses a very interesting tool for helping point out who
> entered a bug in the compiler after doing a change.
>
> The tool works by keeping track of who modified the files since the
> last build, and what were the changes in the number of regression
> tests. If you modify a file lets say, that introduces a regression in
> the automated tests, you will receive an email notification containing
> information like what were the changes you've done, an what are the
> regressions introduced because of them. The message is also posted on
> a mailing list to keep others updated as well. Since many people can
> update the code since the last build besides you, it is also possible
> you receive a notification even though somebody else broke the
> code. The approximation however is good enough in most cases.
>
> Check out the gcc-regression mailing list to see how things work:
>
> http://gcc.gnu.org/ml/gcc-regression/
>
> Would it be possible to have a similar setup for GUMP? I know this
> implies keeping track of information between builds, something that
> GUMP doesn't do right now. But I think it will be very useful in
> identifying what are the changes that break things, not only a
> notification that things break.
>
> Regards,
> --
> Ovidiu Predescu <ov...@cup.hp.com>
> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other
stuff)
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>