From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Documentation improvements
Date: Sat, 29 Dec 2012 22:56:37 +0100 [thread overview]
Message-ID: <20121229225637.67ba3f05@skate> (raw)
In-Reply-To: <CAHXCMMJ18_vRvgxRknjpyBu=U7UZjj4aLHB9K6Y5HrHerz58RQ@mail.gmail.com>
Dear Samuel Martin,
On Sat, 29 Dec 2012 22:17:44 +0100, Samuel Martin wrote:
> Great work! :-)
Thanks for your review!
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-29 21:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 14:42 [Buildroot] Documentation improvements Thomas Petazzoni
2012-12-29 14:42 ` [Buildroot] [PATCH 1/7] docs/manual: add a new 'Details on Buildroot configuration' section Thomas Petazzoni
2012-12-29 21:23 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 2/7] docs/manual: Slightly improve the introduction Thomas Petazzoni
2012-12-29 21:23 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 3/7] docs/manual: add details on toolchain configuration Thomas Petazzoni
2012-12-29 21:27 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 4/7] docs/manual: remove FAQ entry about 'depends on' vs. 'select' Thomas Petazzoni
2012-12-29 21:29 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 5/7] docs/manual: remove incorrect prerequites Thomas Petazzoni
2012-12-29 21:30 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 6/7] docs/manual: mention Java-related optional dependencies Thomas Petazzoni
2012-12-29 21:30 ` Samuel Martin
2012-12-29 14:42 ` [Buildroot] [PATCH 7/7] docs/manual: do not suggest to create a symlink for shared download directory Thomas Petazzoni
2012-12-29 21:30 ` Samuel Martin
2012-12-29 21:17 ` [Buildroot] Documentation improvements Samuel Martin
2012-12-29 21:56 ` Thomas Petazzoni [this message]
2012-12-29 21:43 ` Peter Korsgaard
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=20121229225637.67ba3f05@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