All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] news.html: announce dev days report / next dev days
Date: Sat, 17 Nov 2012 22:41:43 +0100	[thread overview]
Message-ID: <20121117214205.E412B9A080@busybox.osuosl.org> (raw)

commit: http://git.buildroot.net/buildroot/commit/?id=e4f33d4a8c08eca2668320a97dbdd157bbb5ecd4
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 docs/news.html |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/docs/news.html b/docs/news.html
index 2f54567..416857c 100644
--- a/docs/news.html
+++ b/docs/news.html
@@ -5,6 +5,21 @@
 <p>
 
 <ul>
+  <li><b>17 November 2012 -- Buildroot Developer Day</b>
+
+    <p>A report from the recent <i>Buildroot Developer Days</i> meeting
+    in Barcelona, Spain is now <a
+    href="http://lists.busybox.net/pipermail/buildroot/2012-November/061558.html">available</a>.
+    Many thanks to all the participants, and a special thanks to Arnout
+    Vandecappelle from <a href="http://mind.be/">mind</a> for taking
+    notes and Thomas Petazzoni from <a
+    href="http://free-electrons.com/">Free Electrons</a> for handling
+    all the practical arrangements, and naturally our sponsors, <a
+    href="http://www.fluendo.com/">Fluendo</a> and <a href="http://www.synopsys.com/">Synopsis</a>.
+    </p>
+    <p>The next Developer Days will take place on February 4th and 5th
+    in Brussels, Belgium, right after <a href="http://fosdem.org">FOSDEM</a>.</p>
+
    <li><b>31 August 2012 -- 2012.08 released</b>
 
     <p>The stable 2012.08 release is out - Thanks to everyone

                 reply	other threads:[~2012-11-17 21:41 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=20121117214205.E412B9A080@busybox.osuosl.org \
    --to=jacmet@sunsite.dk \
    --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 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.