From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] providing post-build scripts in buildroot
Date: Fri, 8 Mar 2013 12:30:13 +0100 (CET) [thread overview]
Message-ID: <1787200172.233322.1362742213566.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20130308115829.700879e1@skate>
>
> I don't have a strong opinion on this, but doesn't this belongs to
> the
> documentation instead?
>
i'm not sure what you mean here... do you want the script mentionned
in the documentation ? in that case yes, that makes sense
do you want the script "directly included as text" in the doc ?
I am less convinced, unless you want to use them as examples rather
than tools provided by the poject....
next prev parent reply other threads:[~2013-03-08 11:30 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 [this message]
2013-03-08 12:12 ` Thomas Petazzoni
2013-03-08 13:21 ` Jeremy Rosen
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=1787200172.233322.1362742213566.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