From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Raspaudio : how to use buildroot as a git submodule
Date: Thu, 16 Oct 2014 10:18:46 +0200 (CEST) [thread overview]
Message-ID: <515967550.26643419.1413447526264.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <543EB21D.30408@mind.be>
Cordi
----- Mail original -----
> On 08/10/14 12:11, Jeremy Rosen wrote:
> >> >
> > it would be handy to have multiple overlays, but it's not possible
> > with
> > the current buildroot infrastructure...
>
> You're talking about the rootfs overlay, right? BR2_ROOTFS_OVERLAY
> can be a
> space-separated list of overlay directories.
>
yeah, I realized that recently while re-reading the docs... thx for
pointing it out anyway.
> Regards,
> Arnout
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR
> Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
>
prev parent reply other threads:[~2014-10-16 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1436673405.11266711.1394440215222.JavaMail.root@openwide.fr>
2014-03-10 9:00 ` [Buildroot] Raspaudio : how to use buildroot as a git submodule Jeremy Rosen
2014-03-10 15:30 ` Alvaro Gamez
2014-03-10 15:38 ` Jeremy Rosen
2014-09-26 9:00 ` Alvaro Gamez
2014-09-26 11:56 ` Jeremy Rosen
2014-10-01 9:11 ` Alvaro Gamez
2014-10-01 12:58 ` Jeremy Rosen
2014-10-01 14:08 ` Jeremy Rosen
2014-10-01 14:18 ` Alvaro Gamez
2014-10-01 14:37 ` Jeremy Rosen
2014-10-02 9:53 ` Alvaro Gamez
2014-10-02 10:10 ` Jeremy Rosen
2014-10-03 8:03 ` Jeremy Rosen
2014-10-08 8:19 ` Alvaro Gamez
2014-10-08 10:11 ` Jeremy Rosen
2014-10-15 17:42 ` Arnout Vandecappelle
2014-10-16 8:18 ` 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=515967550.26643419.1413447526264.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 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.