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] Buildroot Developpers' Day 2013
Date: Thu, 17 Oct 2013 17:17:54 +0200	[thread overview]
Message-ID: <20131017171754.2354c3a3@skate> (raw)
In-Reply-To: <OF53A5EA25.AF5C7EBF-ON86257C07.004A718E-86257C07.004C0FF5@rockwellcollins.com>

Dear Ryan Barnett,

On Thu, 17 Oct 2013 08:51:02 -0500, Ryan Barnett wrote:

> > > I have started adding a few items to the list of topics to address
> > > during this event, list which you may find there (needs registration
> > > to the Wiki first):
> > >     http://elinux.org/Buildroot:DeveloperDaysELCE2013
> 
> I see that our SELinux patchsets have now made the list of topic 
> discussions.

Yes. However, I am not sure the discussion at the Buildroot meeting
will really lead to something special. Up to now, there is nothing
controversial / problematic about these patches. They just need to be
reviewed, and progressively merged. The most "controversial" issues
will probably arise when we start working on the real SELinux
integration, not just the packages themselves. But we have another
Buildroot meeting at FOSDEM for this :-)

> I would be interested in this, however, discussion that happens early
> in the day will be difficult for me to attend since it would 3:30am CDT 
> (UTC-05:00) when the meeting begins at 9:30 am (Edinburgh Time). However,
> I could join later. I would probably be able to join around 6am to 
> 6:30am CDT. So if discussion surrounding BR2_EXTERNAL, SELinux Related 
> Packages and Yann's buildroot.config could hold off until then I would
> be willing to participate via a Google Hangout. If we setup a specific
> time for the SELinux related packages, I can probably see if I can't
> convince Clayton Shotwell to also attend.

Let's see what happens with the agenda over the course of the WE, and
if it makes sense, we'll try to schedule a specific time for SELinux
discussion.

Best regards,

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

  reply	other threads:[~2013-10-17 15:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 22:39 [Buildroot] Buildroot Developpers' Day 2013 Yann E. MORIN
2013-10-17 12:32 ` Thomas Petazzoni
2013-10-17 13:25   ` Luca Ceresoli
2013-10-17 13:36     ` Thomas Petazzoni
2013-10-17 13:51   ` Ryan Barnett
2013-10-17 15:17     ` Thomas Petazzoni [this message]
2013-10-17 15:28       ` Jesse Cobra
2013-10-17 20:00         ` Yann E. MORIN
2013-10-17 20:17           ` Ryan Barnett
2013-10-17 19:45       ` Ryan Barnett
2013-10-19  7:56         ` Thomas Petazzoni
2013-10-19 19:42           ` Ryan Barnett
2013-10-20 22:14           ` Luca Ceresoli
2013-10-21 22:03             ` Yann E. MORIN
2013-10-21 22:17               ` Ryan Barnett
2013-10-22 14:03             ` Thomas Petazzoni
2013-10-22 14:41               ` Ryan Barnett
2013-10-25  6:38   ` Thomas De Schampheleire
2013-10-25  7:18     ` Thomas Petazzoni
2013-10-25 22:08       ` Ryan Barnett
2013-10-25 22:19         ` Jesse Cobra
2013-10-25 22:38         ` Luca Ceresoli

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=20131017171754.2354c3a3@skate \
    --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