From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Documentation improvements
Date: Sat, 29 Dec 2012 22:43:02 +0100 [thread overview]
Message-ID: <87vcbkttzt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1356792153-24033-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 29 Dec 2012 15:42:26 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Hello Samuel,
Thomas> Here is a set of patches that add more details in the documentation
Thomas> about /dev management, init systems and toolchain configuration, as
Thomas> per our discussion a few days ago on IRC.
Thomas> Besides adding information, I've also reorganized things a bit. I
Thomas> think the "Embedded basics" subsection was really misplaced in "Going
Thomas> further in Buildroot?s innards" section. Knowing the basics is really
Thomas> not something that should be in the "Going further" part.
Thomas> So what I've done is create a "Details of Buildroot configuration"
Thomas> sub-section in the "Working with Buildroot" section (chapter 3), and
Thomas> I've reorganized here the information coming from "Embedded
Thomas> basics". I've removed a few things that are really not Buildroot
Thomas> specific, and I've extended that with more details on toolchain, /dev
Thomas> and init.
Thomas> I also include some unrelated minor fixes to the documentation, as
Thomas> separate patches.
Committed series, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-12-29 21:43 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
2012-12-29 21:43 ` Peter Korsgaard [this message]
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=87vcbkttzt.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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