From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH] update techboard minutes
Date: Tue, 30 Jun 2020 09:19:26 +0200 [thread overview]
Message-ID: <4a99b674-b516-c2a5-7315-8dec13fc4455@redhat.com> (raw)
In-Reply-To: <2019571.ZdL7XmAfXz@thomas>
On 6/30/20 9:17 AM, Thomas Monjalon wrote:
> 30/06/2020 09:07, Maxime Coquelin:
>> --- a/content/techboard/minutes.md
>> +++ b/content/techboard/minutes.md
>> @@ -16,6 +16,8 @@ The [Technical Board](/techboard/)
>> sends minutes of its meetings on the mailing list.
>> They are listed below.
>>
>> +* [2020-06-17](//mails.dpdk.org/archives/dev/2020-June/172108.html)
>> +* [2020-06-05](//mails.dpdk.org/archives/dev/2020-June/169667.html)
>
> I think it was June 3rd
>
Good catch, posting v2.
Thanks,
Maxime
next prev parent reply other threads:[~2020-06-30 7:19 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 7:07 Maxime Coquelin
2020-06-30 7:17 ` Thomas Monjalon
2020-06-30 7:19 ` Maxime Coquelin [this message]
2020-06-30 7:20 ` [dpdk-web] [PATCH v2] " Maxime Coquelin
2020-06-30 7:22 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2021-08-16 9:41 [dpdk-web] [PATCH] " Ferruh Yigit
2021-09-10 14:17 ` Thomas Monjalon
2021-05-25 11:55 Olivier Matz
2021-07-14 15:11 ` Thomas Monjalon
2021-05-19 13:13 Thomas Monjalon
2021-05-19 13:15 ` Thomas Monjalon
2021-02-22 9:09 Ferruh Yigit
2021-02-24 8:32 ` Thomas Monjalon
2020-10-09 0:09 Honnappa Nagarahalli
2020-09-28 16:43 Ferruh Yigit
2020-09-28 21:02 ` Thomas Monjalon
2020-07-27 14:15 Thomas Monjalon
2020-07-10 15:25 Olivier Matz
2020-07-27 14:44 ` Thomas Monjalon
2020-02-19 17:36 Thomas Monjalon
2019-12-16 11:21 Thomas Monjalon
2019-12-16 16:46 ` Honnappa Nagarahalli
2019-12-19 20:45 ` Thomas Monjalon
2019-06-25 15:21 Thomas Monjalon
2019-04-03 12:29 Maxime Coquelin
2019-04-03 13:45 ` Thomas Monjalon
2019-05-08 14:57 ` Thomas Monjalon
2019-02-25 15:06 Thomas Monjalon
2019-02-25 15:10 ` Hemant Agrawal
2019-02-25 15:21 ` Thomas Monjalon
2019-01-22 16:49 Thomas Monjalon
2019-01-25 14:43 ` Thomas Monjalon
2018-12-19 17:08 Thomas Monjalon
2018-12-03 22:04 Thomas Monjalon
2018-12-03 22:42 ` Richardson, Bruce
2018-12-04 0:14 ` Ferruh Yigit
2018-12-04 0:26 ` Thomas Monjalon
2018-09-12 12:56 Thomas Monjalon
2018-06-13 15:30 Thomas Monjalon
2018-03-26 12:37 Thomas Monjalon
2018-02-21 8:31 Olivier Matz
2018-02-21 8:57 ` Thomas Monjalon
2018-02-13 10:30 Olivier Matz
2018-02-13 10:52 ` Thomas Monjalon
2017-11-30 12:08 Yuanhan Liu
2017-11-30 13:18 ` Thomas Monjalon
2017-11-07 3:12 Thomas Monjalon
2017-11-07 8:51 ` Thomas Monjalon
2017-10-25 8:18 Olivier Matz
2017-10-25 8:47 ` Mcnamara, John
2017-10-25 8:53 ` Thomas Monjalon
2017-09-22 17:28 Konstantin Ananyev
2017-09-22 18:46 ` Thomas Monjalon
2017-09-06 3:06 Jerin Jacob
2017-09-06 7:15 ` Thomas Monjalon
2017-07-10 5:37 Yuanhan Liu
2017-07-10 7:19 ` Thomas Monjalon
2017-06-23 9:52 Thomas Monjalon
2017-06-23 9:57 ` Richardson, Bruce
2017-06-23 10:05 ` Thomas Monjalon
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=4a99b674-b516-c2a5-7315-8dec13fc4455@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
--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).