From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] fix year in techboard minutes
Date: Tue, 13 Jun 2023 18:06:48 +0200 [thread overview]
Message-ID: <20230613160648.1281190-1-thomas@monjalon.net> (raw)
The minutes of this year were referenced as last year.
Fixes: 9eb0f97316c1 ("update techboard minutes")
Fixes: 51dbfe82396d ("update techboard minutes")
Reported-by: Bruce Richardson <bruce.richardson@intel.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/techboard/minutes.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/techboard/minutes.md b/content/techboard/minutes.md
index ee6e710..0409141 100644
--- a/content/techboard/minutes.md
+++ b/content/techboard/minutes.md
@@ -24,16 +24,16 @@ The [Technical Board](/techboard/)
sends minutes of its meetings on the mailing list.
They are listed below.
-* [2022-05-17](//mails.dpdk.org/archives/dev/2023-May/269455.html)
-* [2022-05-03](//mails.dpdk.org/archives/dev/2023-May/268136.html)
-* [2022-04-19](//mails.dpdk.org/archives/dev/2023-May/268609.html)
-* [2022-04-05](//mails.dpdk.org/archives/dev/2023-April/266626.html)
-* [2022-03-22](//mails.dpdk.org/archives/dev/2023-March/265703.html)
-* [2022-03-08](//mails.dpdk.org/archives/dev/2023-March/265204.html)
-* [2022-02-22](//mails.dpdk.org/archives/dev/2023-February/263516.html)
-* [2022-02-08](//mails.dpdk.org/archives/dev/2023-May/268225.html)
-* [2022-01-25](//mails.dpdk.org/archives/dev/2023-January/260035.html)
-* [2022-01-11](//mails.dpdk.org/archives/dev/2023-May/267657.html)
+* [2023-05-17](//mails.dpdk.org/archives/dev/2023-May/269455.html)
+* [2023-05-03](//mails.dpdk.org/archives/dev/2023-May/268136.html)
+* [2023-04-19](//mails.dpdk.org/archives/dev/2023-May/268609.html)
+* [2023-04-05](//mails.dpdk.org/archives/dev/2023-April/266626.html)
+* [2023-03-22](//mails.dpdk.org/archives/dev/2023-March/265703.html)
+* [2023-03-08](//mails.dpdk.org/archives/dev/2023-March/265204.html)
+* [2023-02-22](//mails.dpdk.org/archives/dev/2023-February/263516.html)
+* [2023-02-08](//mails.dpdk.org/archives/dev/2023-May/268225.html)
+* [2023-01-25](//mails.dpdk.org/archives/dev/2023-January/260035.html)
+* [2023-01-11](//mails.dpdk.org/archives/dev/2023-May/267657.html)
* 2022-12-14
* [2022-11-30](//mails.dpdk.org/archives/dev/2023-January/259812.html)
* [2022-11-16](//mails.dpdk.org/archives/dev/2023-January/259220.html)
--
2.40.1
next reply other threads:[~2023-06-13 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:06 Thomas Monjalon [this message]
2023-06-13 16:11 ` Richardson, Bruce
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=20230613160648.1281190-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=web@dpdk.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).