Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On Thu, May 2, 2013 at 11:49 AM, Bjoern Michaelsen
<bjoern.michaelsen@canonical.com> wrote:
Hi,

On Wed, May 01, 2013 at 09:33:49PM +0200, Bjoern Michaelsen wrote:
depending on time of day you find 50-90% patch mails on there. As the writer of
mail forward I have been repeatedly asked if we can kill this spam.

so collecting the feedback so far, here is a proposal:

- move the gerrit mails to a separate list

And I re-iterate my earlier question: what is left on the dev ML ?
chatter without patches ?

  - since we now have an opt-in channel, we also mail about comments to changes
    on that list, not only if there is a new proposal

I would suggest to find a way to filter-put auto generated comment,
due to gerrit (like 'has been rebased'... and most of the gerrit
buildbot generated one... except the final 'result' one)

- in addition, aim for a daily digest to the dev-list

If one want a daily digest of a list, one can subscribe in that mode
to that list.. no need to inflict one on everybody by default.

Norbert

PS: the idea of being able to post a comment in gerrit via the ML
seems interesting. Not sure how to do that best and spam-free... but
still that would be a nice improvement to the ML workflow (and make
the [PATCH] message generated by gerrit more relevant... and in turn
make it compeling to keep them in the regular dev ML

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.