All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: TSC / OE Workgroup meeting today
Date: Tue, 03 Jun 2014 10:51:58 +0100	[thread overview]
Message-ID: <1401789118.12440.62.camel@ted> (raw)

Its the first week of the month so there should be a public OpenEmbedded
TSC/workgroup IRC meeting today. If you're interested in discussing
long-term technical efforts around the OpenEmbedded project please join
us on irc.freenode.net in channel #oe. Timing is a little tricky as
today, whilst I can make the old time of 17:00 GMT (9am PST, 11am CST,
12 EST, 18:00 CET) I can't make the later timeslot we moved to which was
2 hours later. I think Paul may not be around today.

I therefore plan to be around at the 17:00 time slot and am happy to
talk with anyone then, the other TSC members may be around then or at
the later time slot.

Cheers,

Richard



             reply	other threads:[~2014-06-03  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03  9:51 Richard Purdie [this message]
2014-06-03 15:07 ` [OE-core] TSC / OE Workgroup meeting today Jeff Osier-Mixon

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=1401789118.12440.62.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.