From: "akuster" <akuster808@gmail.com>
To: Jon Mason <jdmason@kudzu.us>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [OE-core] OpenEmbedded Workshop at FOSDEM20 schedule
Date: Thu, 9 Jan 2020 15:36:51 -0800 [thread overview]
Message-ID: <fb6cfdad-45e5-7cb5-e4a1-f9f62f6b5adf@gmail.com> (raw)
In-Reply-To: <CAPoiz9whfiTNqdM4WVLxrFHkhZHLnapPi+56o2sByra2P6USQA@mail.gmail.com>
On 1/9/20 2:28 PM, Jon Mason wrote:
> The OpenEmbedded Workshop 2020 schedule is now available
> https://pretalx.com/oe-workshop-2020/schedule/
>
> As you can see, there are some very compelling talks. Buy your
> tickets now, before we sell out.
> https://pretix.eu/OpenEmbedded/oe-workshop-2020/
This looks great. Thanks to everyone who is making this happen.
- armin
>
> Thank you,
> The OpenEmbedded Board
prev parent reply other threads:[~2020-01-09 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 22:28 OpenEmbedded Workshop at FOSDEM20 schedule Jon Mason
2020-01-09 23:36 ` akuster [this message]
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=fb6cfdad-45e5-7cb5-e4a1-f9f62f6b5adf@gmail.com \
--to=akuster808@gmail.com \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).