From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] docs/website: update for 2022.02.11
Date: Sun, 19 Mar 2023 14:58:53 +0100 [thread overview]
Message-ID: <20230319140059.856EE8734F@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=48781ec9604834a8e5f0acbe2d71a0c469b54fed
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
docs/website/news.html | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/docs/website/news.html b/docs/website/news.html
index 05d06c6d96..257678465a 100644
--- a/docs/website/news.html
+++ b/docs/website/news.html
@@ -9,6 +9,25 @@
<h2>News</h2>
<ul class="timeline">
+ <li class="timeline-inverted">
+ <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div>
+ <div class="timeline-panel">
+ <div class="timeline-heading">
+ <h4 class="timeline-title">2022.02.11 released</h4>
+ <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>19 March 2023</small></p>
+ </div>
+ <div class="timeline-body">
+ <p>The 2022.02.11 bugfix release is out, fixing a number of important /
+ security related issues discovered since the 2022.02.10 release. See the
+ <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2022.02.11">CHANGES</a>
+ file for more details, read the
+ <a href="https://lore.kernel.org/buildroot/874jqhxbnr.fsf@dell.be.48ers.dk/T/#u">announcement</a>
+ and go to the <a href="/downloads/">downloads page</a> to pick up the
+ <a href="/downloads/buildroot-2022.02.11.tar.xz">2022.02.11 release</a>.</p>
+ </div>
+ </div>
+ </li>
+
<li>
<div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div>
<div class="timeline-panel">
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2023-03-19 14:01 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=20230319140059.856EE8734F@busybox.osuosl.org \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.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).