Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Review of FOSDEM 2014 meeting action points
Date: Wed, 8 Oct 2014 18:14:44 +0200	[thread overview]
Message-ID: <20141008181444.7a45d243@free-electrons.com> (raw)
In-Reply-To: <1490631735.26304543.1412767037821.JavaMail.root@openwide.fr>

Dear Jeremy Rosen,

On Wed, 8 Oct 2014 13:17:17 +0200 (CEST), Jeremy Rosen wrote:

> >  - Evaluation of BR2_EXTERNAL. Not sure exactly what was needed
> >    here. Jeremy Rosen was supposed to submit a patch, but I'm not
> >    sure
> >    if it happened, or even if something needs to happen.
> > 
> 
> The patch was more or less deprecated/implemented differently.
> 
> buildroot-submodules covers the underlying idea of that particular 
> action point : how complete is BR2_EXTERNAL, can we externalize 
> everything ? at this point, the answer is definitely yes, so
> this can be considered closed

Ok, thanks for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-08 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  8:48 [Buildroot] Review of FOSDEM 2014 meeting action points Thomas Petazzoni
2014-10-08  8:54 ` Samuel Martin
2014-10-08 11:01   ` Maxime Hadjinlian
2014-10-08 16:14     ` Thomas Petazzoni
2014-10-08 16:24       ` Gustavo Zacarias
2014-10-08 16:18   ` Thomas Petazzoni
2014-10-08 11:17 ` Jeremy Rosen
2014-10-08 16:14   ` Thomas Petazzoni [this message]
2014-10-08 11:43 ` Thomas De Schampheleire
2014-10-08 16:16   ` Thomas Petazzoni
2014-10-08 16:40 ` Matthew Weber
2014-10-08 16:43   ` 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=20141008181444.7a45d243@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox