All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Slides "Using Buildroot for real projects"
Date: Fri, 21 Oct 2011 15:33:30 +0100	[thread overview]
Message-ID: <4EA182BA.2050400@carallon.com> (raw)
In-Reply-To: <20111021154303.43f98ccd@skate>

On 21/10/2011 14:43, Thomas Petazzoni wrote:
> Le Mon, 17 Oct 2011 18:47:18 +0200,
> Thomas Petazzoni<thomas.petazzoni@free-electrons.com>  a ?crit :
>
>> The current (unfinished) status of my slides is visible at:
>>    http://free-electrons.com/~thomas/pub/using-buildroot-real-project.pdf
<snip>
> Now, if you're still willing to spend some time on this, I'd like to
> have comments on:
>   * remaining english typos, wording improvements, etc.

Couple of minor points on the English (Still very impressive from a non 
native speaker)
p8: "Buildroot starts by the toolchain" should be "starts with the"
p16 "Any other project specific file" should perhaps be "files"
p17: "kernel and bootloaders often" shouldn't it be singular bootloader?
p17: "drawback is that Buildroot does directly" unless I misunderstand 
the use case, don't you mean doesn't?
p21: "I don't recommend this, ..." I'm not sure if you are not 
recommending changing the skeleton or using a script to modify it
p30: "finds automagically" should be "automagically finds"
p37: "assignements" should be assignments
p37: "allows to tell" should be "allows you to tell"

>   * suggestions of additional contents/topics if there is something I
>     missed. Like if you use best practices that aren't described in
>     those slides.

One thing I'd love to get written up somewhere is best practice for NFS 
mounting a filesystem image, but I realise this may not be relevant to 
your talk.

Otherwise your slides are very good at explaining how it all works.

Will

  parent reply	other threads:[~2011-10-21 14:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 16:47 [Buildroot] [RFC] Slides "Using Buildroot for real projects" Thomas Petazzoni
2011-10-17 21:13 ` Peter Korsgaard
2011-10-18  7:26 ` Baruch Siach
2011-10-21 13:44   ` Thomas Petazzoni
2011-10-18  9:22 ` Thomas De Schampheleire
2011-10-18 21:35 ` Arnout Vandecappelle
2011-10-19  6:29   ` Thomas De Schampheleire
2011-10-21 13:43 ` Thomas Petazzoni
2011-10-21 13:51   ` Yegor Yefremov
2011-10-21 13:58     ` Thomas Petazzoni
2011-10-21 14:24       ` Yegor Yefremov
2011-10-21 15:34         ` Thomas Petazzoni
2011-10-21 14:33   ` Will Wagner [this message]
2011-10-21 15:25     ` Thomas Petazzoni
2011-10-22 17:04   ` Thomas De Schampheleire
2011-10-23 12:37   ` Baruch Siach
2011-10-24 15:32     ` Thomas Petazzoni
2011-10-24 16:42       ` Yann E. MORIN
2011-10-24 17:17         ` 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=4EA182BA.2050400@carallon.com \
    --to=will_wagner@carallon.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.