From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Splitting this list
Date: Tue, 18 Sep 2012 08:21:09 +0200 [thread overview]
Message-ID: <87ehlzonqi.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAJpxd05FN2NVVaQ2CAMkpRDvazFiqhSAqBEOgd+=Yc9JrDbZgA@mail.gmail.com> (Bryce Schober's message of "Mon, 17 Sep 2012 11:58:21 -0700")
>>>>> "Bryce" == Bryce Schober <bryce.schober@gmail.com> writes:
Bryce> It seems to me that this list could benefit from a split to
Bryce> buildroot-user & buildroot-dev. There's an awful lot of
Bryce> developer "noise" for those trying to get off the ground and get
Bryce> working. Just a thought...
We've considered it in the past, but so far the feeling among the main
developers favors a single list.
Another proposal than -user / -dev was to move the git commit mails to a
seperate list, which was brought up recently.
But splitting the list can also bring disadvantages, so I would prefer
to keep it like it is, unless a lot of people think elsewise?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-09-18 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 18:58 [Buildroot] Splitting this list Bryce Schober
2012-09-18 6:21 ` Peter Korsgaard [this message]
2012-09-18 14:25 ` Thomas Petazzoni
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=87ehlzonqi.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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