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 Hackathon on August 1-2-3-4
Date: Thu, 27 Jun 2019 10:50:56 +0200	[thread overview]
Message-ID: <20190627105056.0484ceab@windsurf> (raw)

Hello,

Some of the core Buildroot developers will meet on August 1-2-3-4 in
Toulouse (France) for a Buildroot hackathon. This event is reserved to
a small core team of Buildroot developers, and therefore is not open to
everybody like the Buildroot Developers Meeting I announced in a
previous e-mail.

However, we believe it is quite important to announce this hackathon
publicly, so that the entire community knows that there will be a burst
of activity on August 1-2-3-4. Some of you may be interested in
resending some patch series for this date so that they can be
considered for review/discussion during the hackathon. We will also be
available on IRC during the hackathon, so you can also participate
remotely to the patch review effort.

Best regards,

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

                 reply	other threads:[~2019-06-27  8:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190627105056.0484ceab@windsurf \
    --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