I reduced the autobuild report from 200 to 20 lines. That should help. I was hoping to have the autobuild reports not in the digest so that they are more apparent.
The idea is that if someone checks something in, the next day, they should check to make sure nothing broke. If something broke, then it should be fixed. Ideally we'd have buildbot setup. It can email the specific person who broke compilation. But that's a big project.
I have to say that I am very surprised that the autobuilds aren't being used by vibrez/devel, especially when working towards a release. It makes that job much, much easier.
.hc
On Nov 28, 2006, at 6:31 AM, Thomas Grill wrote:
Hi all, would it be possible to exclude the autobuild results from this digest, like e.g. by making a separate mailing for that. It's has become absolutely impossible to track the cvs changes.
Anfang der weitergeleiteten E-Mail:
! ## Something's wrong here: ! ##
#--------------------------------------------------------------------
...
! ## $(scripts_src)/generate-libdir-metafile.sh $(objectsdir) $ (RTC-LIB_NAME) \ ! ## --author "Karlheinz Essel and Frank Barknecht" \
Hi Frank, somethinge's definitely wronge here.
best greetings, Thomas
-- Thomas Grill http://grrrr.org
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.