+1!!
----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 1 Apr 2014 17:45:05 -0500
> From: "David Lu!!" <davidlu@wustl.edu>
> To: ros-release@code.ros.org
> Subject: [ros-release] Fwd: Torrents of Emails
> Message-ID:
> <CABd+9SqtEdzDXEEhaHT=2V8Xb7B1ofi2Tq8Lo4SvU3b7z=
> ZGBw@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> So I'd like to start a hopefully constructive discussion of the build
> farm's email practices. I've attached a picture of the onslaught my
> inbox just received. I'm fairly certain none of the builds failing is
> my fault. But it does lead me to some questions.
>
> 1) Are there settings for email that I haven't set to reduce the
> number of emails I get? Or am I automatically subscribed because I'm a
> maintainer?
> 2) Is there a way to condense the emails? If I got a single email
> telling me which packages I maintain failed to build, but this seems a
> bit much.
> 3) I've whined about this before, but is there some way we can make
> the error messages more legible? I'm sure for people familiar with the
> build farm, the errors may make sense, but as a maintainer, I have no
> idea what I'm supposed to do. If the answer is nothing, why am I
> getting email?
>
> I realize accomplishing some of these tasks will likely involve
> substantial amounts of work, but I feel it merits discussion
> nonetheless.
>
> -David
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Screenshot from 2014-04-01 17:30:36.png
> Type: image/png
> Size: 635975 bytes
> Desc: not available
> URL: <
> http://lists.ros.org/pipermail/ros-release/attachments/20140401/9ae7884d/attachment.png
> >
>
> ------------------------------
>
> _______________________________________________
> ros-release mailing list
> ros-release@code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>
> End of ros-release Digest, Vol 30, Issue 2
> ******************************************
>
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
%20Are%20there%20settings%20for%20email%20that%20I%20haven't%20set%20to%20reduce%20the%0A>%20>%20number%20of%20emails%20I%20get?%20Or%20am%20I%20automatically%20subscribed%20because%20I'm%20a%0A>%20>%20maintainer?%0A>%20>%202)%20Is%20there%20a%20way%20to%20condense%20the%20emails?%20If%20I%20got%20a%20single%20email%0A>%20>%20telling%20me%20which%20packages%20I%20maintain%20failed%20to%20build,%20but%20this%20seems%20a%0A>%20>%20bit%20much.%0A>%20>%203)%20I've%20whined%20about%20this%20before,%20but%20is%20there%20some%20way%20we%20can%20make%0A>%20>%20the%20error%20messages%20more%20legible?%20I'm%20sure%20for%20people%20familiar%20with%20the%0A>%20>%20build%20farm,%20the%20errors%20may%20make%20sense,%20but%20as%20a%20maintainer,%20I%20have%20no%0A>%20>%20idea%20what%20I'm%20supposed%20to%20do.%20If%20the%20answer%20is%20nothing,%20why%20am%20I%0A>%20>%20getting%20email?%0A>%20>%0A>%20>%20I%20realize%20accomplishing%20some%20of%20these%20tasks%20will%20likely%20involve%0A>%20>%20substantial%20amounts%20of%20work,%20but%20I%20feel%20it%20merits%20discussion%0A>%20>%20nonetheless.%0A>%20>%0A>%20>%20-David%0A>%20>%20--------------%20next%20part%20--------------%0A>%20>%20A%20non-text%20attachment%20was%20scrubbed...%0A>%20>%20Name:%20Screenshot%20from%202014-04-01%2017:30:36.png%0A>%20>%20Type:%20image/png%0A>%20>%20Size:%20635975%20bytes%0A>%20>%20Desc:%20not%20available%0A>%20>%20URL:%20<%0A>%20>%20http://lists.ros.org/pipermail/ros-release/attachments/20140401/9ae7884d/attachment.png%0A>%20>%20>%0A>%20>%0A>%20>%20------------------------------%0A>%20>%0A>%20>%20_______________________________________________%0A>%20>%20ros-release%20mailing%20list%0A>%20>%20ros-release@code.ros.org%0A>%20>%20http://lists.ros.org/mailman/listinfo/ros-release%0A>%20>%0A>%20>%0A>%20>%20End%20of%20ros-release%20Digest,%20Vol%2030,%20Issue%202%0A>%20>%20******************************************%0A>%20>%0A>%20_______________________________________________%0A>%20ros-release%20mailing%20list%0A>%20ros-release@code.ros.org%0A>%20http://lists.ros.org/mailman/listinfo/ros-release%0A>%20 "Besvar denne besked")
(text/plain)