From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] providing post-build scripts in buildroot
Date: Fri, 8 Mar 2013 14:21:53 +0100 (CET) [thread overview]
Message-ID: <520542980.236150.1362748913901.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20130308131203.2a847c24@skate>
> Yes, the scripts included directly into the documentation. At the
> last
> Buildroot meeting, we've discussed the idea of extending the
> documentation with more "Use cases descriptions", i.e how to use
> Buildroot in practice for a project. I think examples of what can be
> done in post-build scripts who fit quite well in this.
>
ok, thx
i'll get my scripts into an upstreamable shape and include them in the documentation
prev parent reply other threads:[~2013-03-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1890922777.231675.1362739947331.JavaMail.root@openwide.fr>
2013-03-08 10:55 ` [Buildroot] providing post-build scripts in buildroot Jeremy Rosen
2013-03-08 10:58 ` Thomas Petazzoni
2013-03-08 11:30 ` Jeremy Rosen
2013-03-08 12:12 ` Thomas Petazzoni
2013-03-08 13:21 ` Jeremy Rosen [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=520542980.236150.1362748913901.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--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