From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developpers' Day 2013
Date: Mon, 21 Oct 2013 00:14:51 +0200 [thread overview]
Message-ID: <526455DB.4040102@lucaceresoli.net> (raw)
In-Reply-To: <20131019095649.5493a6be@skate>
Hi Thomas,
Thomas Petazzoni wrote:
> Dear Ryan Barnett,
>
> On Thu, 17 Oct 2013 14:45:24 -0500, Ryan Barnett wrote:
>
>>> 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.
>>
>> That sounds good, I'm more interested in being able to listen in on Yann's
>> buildroot.config and being a part of the discussion for BR2_EXTERNAL.
>> We (Rockwell Collins) have been starting to use the patchset on some new
>> projects so I could probably put together something about our experience.
>> Would there be interest in hearing about how we are using and how it has
>> changed our approach to development? So it would be nice if these could be
>> later or at least have a rough estimate of when they will start.
>
> Ok. Seems like there are at least two interested persons. Let's say
> we're going to schedule those two topics (Yann's presentation, and
> BR2_EXTERNAL discussion) at 3:00 PM UTC (which is local time in
> Edinburgh), which would be 10:00 AM EST I believe.
Sure? On Saturday 26 Edinburgh time will still be BST (British Summer
Time), which is UTC+1, not UTC. That's for DST (daylight saving time)
which ends one day later, on Sunday 27.
So I guess you really meant:
Edinburgh (BST = UTC+1): 3:00 PM
Rome/Paris (CEST = UTC+2): 4:00 PM (me)
Chicago (CDT = UTC-5): 9:00 AM (Ryan timezone, correct?)
Am I correct?
Oh, look here, that should explain much better:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=BDD+Hangout&iso=20131026T15&p1=304&ah=1
>
> Would this be ok?
Under the above asumptions, it will.
I'll be available between 3:00 PM and 5:00 PM CEST (Italy/France),
meaning 2:00 PM to 4:00 PM BST (Edinburgh).
Under the above assumptions, that means I'll have a 1 hour time window
since the starting time, and leave you at 4:00 PM Edinburgh Time (5:00
PM Italian time).
--
Luca
next prev parent reply other threads:[~2013-10-20 22:14 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
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 [this message]
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=526455DB.4040102@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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