From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] suggestion?
Date: Wed, 27 Jan 2016 13:22:07 +0100 [thread overview]
Message-ID: <20160127132207.2372b7a4@free-electrons.com> (raw)
In-Reply-To: <09ad01d158fa$a6f7c8e0$f4e75aa0$@chordia.co.uk>
Hello Jerry,
On Wed, 27 Jan 2016 12:02:53 -0000, jerry at chordia.co.uk wrote:
> How about a buildroot-user list? Or is there a better place to go for help
> using BR as opposed to development? Thanks.
We had this discussion a few times during the past Buildroot meetings,
and our position is that in terms of Buildroot, the boundary between
"user" and "developer" is clearly not as clear-cut as for many other
programs. Indeed, a user very often needs to add his own packages
(either to package his own custom applications/libraries, or to package
open-source applications/libraries that are not yet in Buildroot),
which makes this user almost immediately a developer.
For this reason, we've chosen to keep the entire discussions on one
list. So feel free to ask your user-level questions on this list.
We also have an IRC channel, #buildroot on Freenode, on which you can
very often get live help. Many of the participants are based in Europe,
but I see you're in the UK, so in terms of timezone it should match
pretty well.
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 12:22 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 [this message]
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
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=20160127132207.2372b7a4@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