[Buildroot] Email list volume

[Buildroot] Email list volume

[Bryce Schober]

I realize this is really only an occasional problem, but it would be
helpful to raise the signal-to-noise ratio if this email list didn't also
serve as a git commit log.  I'm just sayin' 1500 emails in a day is a bit
much.

<><  <><  <><
Bryce Schober
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150808/578a4130/attachment.html>

[Buildroot] Email list volume

[Thomas Petazzoni]

Bryce,

On Sat, 8 Aug 2015 12:46:21 -0700, Bryce Schober wrote:
> I realize this is really only an occasional problem, but it would be
> helpful to raise the signal-to-noise ratio if this email list didn't also
> serve as a git commit log.  I'm just sayin' 1500 emails in a day is a bit
> much.

I apologize about today's traffic as it is entirely my fault. I created
the 'next' branch to start merging new packages and major changes even
if we've entered the -rc cycle for 2015.08. And the way I did it ended
up resending a notification e-mail for each commit of the 2015.08-rc1
cycle.

So this 1500 e-mail for today is really exceptional. Though I agree in
general that the volume of traffic on the list is quite high. If you
have suggestions to make it more reasonable, it would definitely be
interesting.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Email list volume

[Bryce Schober]

On Sat, Aug 8, 2015 at 1:32 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> So this 1500 e-mail for today is really exceptional. Though I agree in
> general that the volume of traffic on the list is quite high. If you
> have suggestions to make it more reasonable, it would definitely be
> interesting.
>

It seems to me that I've seen git commits posted here regularly... but
scanning back now, I see that's not actually standard practice lately. I
don't know what I'd do except keep the git commit notifications off the
list, but it appears that's not normal anyway.

<><  <><  <><
Bryce Schober
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150808/8cb5a995/attachment.html>

[Buildroot] Email list volume

[Thomas De Schampheleire]

On August 9, 2015 6:41:20 AM CEST, Bryce Schober <bryce.schober@gmail.com> wrote:
>On Sat, Aug 8, 2015 at 1:32 PM, Thomas Petazzoni <
>thomas.petazzoni at free-electrons.com> wrote:
>
>> So this 1500 e-mail for today is really exceptional. Though I agree
>in
>> general that the volume of traffic on the list is quite high. If you
>> have suggestions to make it more reasonable, it would definitely be
>> interesting.
>>
>
>It seems to me that I've seen git commits posted here regularly... but
>scanning back now, I see that's not actually standard practice lately.
>I
>don't know what I'd do except keep the git commit notifications off the
>list, but it appears that's not normal anyway.

Git commits _are_ posted, one mail per commit. Reducing this to one mail per time
interval (a few hours or one day), with just the list of commits, will reduce the traffic
 significantly.

Of course, there is less visibility on the applied patches, but the original patches
 have already been sent to the list and acked to, and interested people can still
 also refer to git itself...

/Thomas

[Buildroot] Email list volume

[Bernd Kuhls]

Am Sat, 08 Aug 2015 22:32:11 +0200 schrieb Thomas Petazzoni:

> So this 1500 e-mail for today is really exceptional. Though I agree in
> general that the volume of traffic on the list is quite high. If you
> have suggestions to make it more reasonable, it would definitely be
> interesting.

Hi Thomas,

what about creating a second newsgroup for commit messages only? Patches 
should still be sent to this newsgroup and the discussion takes place 
here.

Here are some examples from other projects:

http://news.gmane.org/gmane.comp.apache.cvs
http://news.gmane.org/gmane.comp.emulators.wine.cvs
http://news.gmane.org/gmane.comp.encryption.gpg.cvs
http://news.gmane.org/gmane.comp.freedesktop.xorg.cvs
http://news.gmane.org/gmane.comp.gcc.cvs
http://news.gmane.org/gmane.comp.gnu.binutils.cvs

and many, many other mailinglists ending with ".cvs"

Regards, Bernd

[Buildroot] Email list volume

[Thomas Petazzoni]

Bernd,

On Sun, 09 Aug 2015 10:18:50 +0200, Bernd Kuhls wrote:

> what about creating a second newsgroup for commit messages only? Patches 
> should still be sent to this newsgroup and the discussion takes place 
> here.

I think this has been discussed in past Buildroot meetings, and the
general consensus so far (as far as I remember) is that having the
commit messages in the main mailing list is a good way of giving
visibility to what's going on. People can always create a filter to
move or remove git commit messages if they are really not interested in
seeing them.

That being said, the traffic on the list is high, so maybe we need to
do something about it. As Thomas DS proposed, maybe a summary of the
Git commits can be sent every day (while keeping the one mail per
commit thing for another mailing list, as you suggest).

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Email list volume

[Grant Edwards]

On 2015-08-08, Bryce Schober <bryce.schober@gmail.com> wrote:

> I realize this is really only an occasional problem, but it would be
> helpful to raise the signal-to-noise ratio if this email list didn't also
> serve as a git commit log.  I'm just sayin' 1500 emails in a day is a bit
> much.

You mean there are people who don't filter out the git commit
messages? I point slrn at nntp://news.gmane.org/gmane.comp.lib.uclibc.buildroot
and have this in my .score file:

[gmane.comp.lib.uclibc.buildroot]
Score: =-9999
Subject: \[git commit\]

-- 
Grant Edwards               grant.b.edwards        Yow! Here I am at the flea
                                  at               market but nobody is buying
                              gmail.com            my urine sample bottles ...