From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] suggestion?
Date: Wed, 27 Jan 2016 14:38:57 +0100 [thread overview]
Message-ID: <20160127143857.2f2ea66d@free-electrons.com> (raw)
In-Reply-To: <09f301d15903$563d58d0$02b80a70$@chordia.co.uk>
Hello,
On Wed, 27 Jan 2016 13:05:03 -0000, jerry at chordia.co.uk wrote:
> > http://stackoverflow.com/questions/ask
> > using the new "buildroot" tag rather than asking on this list.
>
> Is there much of a BR community on SO? I guess it works for those mad to
> build rep :)
Unlike what Jonathan said, I wouldn't really suggest to rely on
Stackoverflow. While Stackoverflow was really great at the beginning,
there are now tons of people giving completely incorrect and invalid
answers. On the Buildroot topic fortunately, a few of the core
developers/contributors are monitoring the "buildroot" tag, so they are
giving good answers, but I've also seen other answers that were
completely wrong. Arnout Vandecappelle and Luca Ceresoli are
particularly active at answering Buildroot questions on Stackoverflow.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-27 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 12:02 [Buildroot] suggestion? jerry at chordia.co.uk
2016-01-27 12:22 ` Thomas Petazzoni
2016-01-27 12:31 ` Jonathan Ben Avraham
2016-01-27 13:05 ` jerry at chordia.co.uk
2016-01-27 13:38 ` Thomas Petazzoni [this message]
2016-01-27 18:56 ` jerry at chordia.co.uk
2016-01-28 22:59 ` Arnout Vandecappelle
2016-01-29 1:04 ` jerry at chordia.co.uk
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=20160127143857.2f2ea66d@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