Re: Killing the gerrit to dev-list spam ...

The dev-ML is to discuss code.
code come as patch, and preferably as gerrit patch... so seing the
patch that are proposed via gerrit is the core function of the ML,
just like before gerrit they where posted to the ML .

and yes I agree with Bjoern that the 'pos-facto' email are the less
interesting part...
but the 'heads-up' part _is_ the interesting part for the dev-ML...

If we remove all the [PATCH] from the ML, what is left ? a dev-discuss list ?

Norbert

PS: if you really do not care about [PATCH] it is really not that hard
to set-up filter on your client side....