From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Topics to discuss at the meeting
Date: Fri, 10 Oct 2014 10:07:21 +0200 [thread overview]
Message-ID: <20141010100721.2533ba33@free-electrons.com> (raw)
In-Reply-To: <CAGm1_ksryT=qOg3kJ5wnY31eioxZubQwgz_xOScgsqNDp_j7fg@mail.gmail.com>
Dear Yegor Yefremov,
On Fri, 10 Oct 2014 09:41:57 +0200, Yegor Yefremov wrote:
> > Sure. However, the two persons having expressed some knowledge about
> > FIT are you and Thomas DS, and none of you will be at the meeting.
> >
> > Could you give some examples about the two cases you have (cpio and
> > ext2) and how they cause issues with the current Buildroot? I
> > understand it's a build ordering problem, but I'd like to understand
> > better the use cases of FIT to see how we can solve this.
>
> I've added FIT topic to the TODO list on elinux.org:
> http://elinux.org/Buildroot#Core_Buildroot_infrastructure
Well, if you want the FIT topic to be discussed during the meeting,
that's not the right place. The right place is
http://elinux.org/Buildroot:DeveloperDaysELCE2014, which is the page
dedicated to the meeting.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-10 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:56 [Buildroot] Topics to discuss at the meeting Thomas Petazzoni
2014-10-08 9:10 ` Yegor Yefremov
2014-10-08 16:13 ` Thomas Petazzoni
2014-10-10 7:41 ` Yegor Yefremov
2014-10-10 8:07 ` Thomas Petazzoni [this message]
2014-10-08 11:56 ` Thomas De Schampheleire
2014-10-08 16:12 ` Thomas Petazzoni
2014-10-10 9:50 ` Thomas De Schampheleire
2014-10-10 10:18 ` Thomas Petazzoni
2014-10-12 8:13 ` Luca Ceresoli
2014-10-12 14:41 ` Matthew Weber
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=20141010100721.2533ba33@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