From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 08/12] manual: update get-involved section
Date: Fri, 1 Nov 2013 17:19:56 +0100 [thread overview]
Message-ID: <20131101171956.4eceb638@skate> (raw)
In-Reply-To: <77c7aa6b747b29c2bf0973bf5a80697cf1b8fa4a.1382127504.git.s.martin49@gmail.com>
Dear Samuel Martin,
On Fri, 18 Oct 2013 22:31:32 +0200, Samuel Martin wrote:
> * add events from the html page to the list
> * add "Buildroot material" section. This new section references material
> (video, slides, posters, etc) used during presentations about Buildroot.
I am not convinced we should mix "Buildroot Developers Meeting"
references with other Buildroot talks. While "Buildroot Developers
Meeting" listing definitely has its place in the "Getting involved"
section, the list of Buildroot talks, with pointers to slides and video
is useful for much more than people willing to get deeply involved in
Buildroot development. For example, the last talk from Peter at
ELCE2013, or the talk "Using Buildroot for real projects" I gave a few
years ago, make sense for users.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-01 16:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 20:31 [Buildroot] [pull request] Pull request for branch sma/doc-update Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 01/12] manual generation: check dependencies first Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 02/12] manual generation: rename manual-txt into manual-text Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 03/12] support: trivial fixes (typos and minor rewording) in gen-manual-lists.py Samuel Martin
2013-10-20 7:32 ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 04/12] manual: move the manual rsync directory under $(O)/build/ Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 05/12] manual: developer-guide.txt: cleanup non-existing source Samuel Martin
2013-10-20 19:14 ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 06/12] manual: introduction.txt: enhance Buildroot presentation Samuel Martin
2013-11-01 16:17 ` Thomas Petazzoni
2013-10-18 20:31 ` [Buildroot] [PATCH 07/12] manual: get-involved.txt: fix event order Samuel Martin
2013-11-01 16:18 ` Thomas Petazzoni
2013-11-02 14:54 ` Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 08/12] manual: update get-involved section Samuel Martin
2013-11-01 16:19 ` Thomas Petazzoni [this message]
2013-11-02 15:12 ` Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 09/12] manual: rework Deploying images chapter Samuel Martin
2013-11-01 16:36 ` Thomas Petazzoni
2013-11-06 12:54 ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 10/12] manual: customize-toolchain.txt: update internal backend section Samuel Martin
2013-10-21 6:25 ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 11/12] manual: faq-troubleshooting.txt: add tips to avoid toolchain build Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 12/12] board: add warning to readme files explaining how to flash the target Samuel Martin
2013-10-22 15:13 ` Thomas Petazzoni
2013-11-01 16:12 ` [Buildroot] [pull request] Pull request for branch sma/doc-update Thomas Petazzoni
2013-11-01 21:08 ` Samuel Martin
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=20131101171956.4eceb638@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox