Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Virtual Developers Meeting: Jul 27, Aug 28-29
Date: Wed, 22 Jul 2020 10:34:55 +0200	[thread overview]
Message-ID: <20200722103455.584534b6@windsurf.home> (raw)
In-Reply-To: <20200722100956.5497f0fe@windsurf.home>

On Wed, 22 Jul 2020 10:09:56 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> We will have a virtual Buildroot Developers meeting on the following
> dates:
> 
>  - July 27
>  - August 28
>  - August 29

Here is our traditional Wiki page for this meeting:

  https://elinux.org/Buildroot:VirtualDeveloperDaysSummer2020

If you intend to participate, please indicate your name, on which day
and time you will be available.

Also, whether you intend to participate or not, do not hesitate to fill
in the list of topics to cover with more items.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-07-22  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  8:09 [Buildroot] Buildroot Virtual Developers Meeting: Jul 27, Aug 28-29 Thomas Petazzoni
2020-07-22  8:34 ` Thomas Petazzoni [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=20200722103455.584534b6@windsurf.home \
    --to=thomas.petazzoni@bootlin.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