From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "web@dpdk.org" <web@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] update techboard minute for September 26
Date: Wed, 3 Oct 2018 20:31:15 +0100 [thread overview]
Message-ID: <de5ac364-e07d-120f-ffc8-d7a624e1da9d@intel.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20EEE6773@SHSMSX101.ccr.corp.intel.com>
On 9/29/2018 8:19 AM, Tu, Lijuan wrote:
> I think it is 2018-09-26 but not 2018-08-26
You are right, I will send v2.
Thanks,
ferruh
>
>> -----Original Message-----
>> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Ferruh Yigit
>> Sent: Friday, September 28, 2018 12:29 AM
>> To: Thomas Monjalon <thomas@monjalon.net>
>> Cc: web@dpdk.org; techboard@dpdk.org; Yigit, Ferruh
>> <ferruh.yigit@intel.com>
>> Subject: [dpdk-web] [PATCH] update techboard minute for September 26
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> ---
>> content/techboard/minutes.md | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/content/techboard/minutes.md
>> b/content/techboard/minutes.md index ca4ccf1..6e18789 100644
>> --- a/content/techboard/minutes.md
>> +++ b/content/techboard/minutes.md
>> @@ -16,6 +16,7 @@ The [Technical Board](/techboard/) sends minutes of
>> its meetings on the mailing list.
>> They are listed below.
>>
>> +*
>> +[2018-08-26](//mails.dpdk.org/archives/dev/2018-September/113286.html
>> )
>> * [2018-08-01](//mails.dpdk.org/archives/dev/2018-August/109426.html)
>> * [2018-07-18](//mails.dpdk.org/archives/dev/2018-August/109425.html)
>> * [2018-07-04](//mails.dpdk.org/archives/dev/2018-July/108072.html)
>> --
>> 2.17.1
>
next prev parent reply other threads:[~2018-10-03 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 16:29 Ferruh Yigit
2018-09-29 7:19 ` Tu, Lijuan
2018-10-03 19:31 ` Ferruh Yigit [this message]
2018-10-03 20:34 ` [dpdk-web] [PATCH v2] " Ferruh Yigit
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=de5ac364-e07d-120f-ffc8-d7a624e1da9d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=lijuan.tu@intel.com \
--cc=techboard@dpdk.org \
--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).