From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Email list volume
Date: Sun, 9 Aug 2015 10:48:55 +0200 [thread overview]
Message-ID: <20150809104855.006e22c8@free-electrons.com> (raw)
In-Reply-To: <a0fj9cx87a.ln2@ID-313208.user.individual.net>
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
next prev parent reply other threads:[~2015-08-09 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 19:46 [Buildroot] Email list volume Bryce Schober
2015-08-08 20:32 ` Thomas Petazzoni
2015-08-09 4:41 ` Bryce Schober
2015-08-09 5:46 ` Thomas De Schampheleire
2015-08-09 8:18 ` Bernd Kuhls
2015-08-09 8:48 ` Thomas Petazzoni [this message]
2015-08-11 17:00 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150809104855.006e22c8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox