From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] docs/website: change wording about training provided by Bootlin
Date: Sat, 12 Jun 2021 23:09:43 +0200 [thread overview]
Message-ID: <20210612203850.4FCBA8B367@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=2e1e9d2ebd5d59b3120c2ccfc6571eadb6745e4f
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
As suggested by Yann, let's avoid announcing the exact date of the
next course, as it gets outdated very often. Instead, use a more
generic wording and simply point to a Bootlin page that has all the
details.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
---
docs/website/docs.html | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/docs/website/docs.html b/docs/website/docs.html
index e8d8138565..85b005004d 100644
--- a/docs/website/docs.html
+++ b/docs/website/docs.html
@@ -108,14 +108,13 @@
</div>
<div class="panel panel-default">
- <div class="panel-heading">Public training course</div>
+ <div class="panel-heading">Public online training course</div>
<div class="panel-body">
- The next online public training course on Buildroot
- organized
- by <a href="https://www.bootlin.com">Bootlin</a> will
- take place from May 31 to June 4, 2021, with Thomas Petazzoni as
- trainer. <a href="https://bootlin.com/training/buildroot/">Infos</a>
- and <a href="https://www.eventbrite.com/e/bootlin-embedded-linux-development-with-buildroot-training-seminar-tickets-145276318379">registration</a>.
+ Regular online training courses, available to individual
+ registration, are proposed by Bootlin, with Thomas
+ Petazzoni as
+ trainer. See <a href="https://bootlin.com/training/buildroot/">next
+ dates and registration details</a>.
</div>
</div>
</div>
reply other threads:[~2021-06-12 21:09 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=20210612203850.4FCBA8B367@busybox.osuosl.org \
--to=yann.morin.1998@free.fr \
--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.