From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot at FOSDEM
Date: Tue, 18 Dec 2012 09:38:39 +0100 [thread overview]
Message-ID: <20121218093839.5c356646@skate> (raw)
In-Reply-To: <50D02307.2010906@mind.be>
Dear Arnout Vandecappelle,
On Tue, 18 Dec 2012 09:02:15 +0100, Arnout Vandecappelle wrote:
> Deadlines for FOSDEM are approaching fast (i.e., this Thursday or
> Friday). There are a few devrooms where a buildroot presentation
> would fit:
>
> - Community Development and Marketing: 5, 15 or 30 minute
> presentation about the community process of buildroot.
>
> - Cross-distro devroom: buildroot as a distro, 30 or 60 minutes.
>
> - Testing and Automation devroom: the buildroot autobuilder concept
> in 10 or 30 minutes.
>
> Any takers?
Does it really fit in the "Cross-distro devroom" ? I guess by "Cross"
they don't mean "cross-compilation", but rather exchanges between
distributions such as Gentoo, Fedora, Ubuntu, etc. Does Buildroot
really fit in the middle of those discussions? I believe we have quite
different use cases, needs, requirements, etc.
But in any case, I'm definitely interested in proposing a talk related
to Buildroot. Let's sync on how's going to propose what.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-18 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 8:02 [Buildroot] buildroot at FOSDEM Arnout Vandecappelle
2012-12-18 8:38 ` Thomas Petazzoni [this message]
2012-12-18 9:05 ` Jeremy Rosen
2012-12-18 9:10 ` Thomas Petazzoni
2012-12-18 17:51 ` Arnout Vandecappelle
2012-12-18 21:40 ` 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=20121218093839.5c356646@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.