From: Thomas Monjalon <thomas@monjalon.net>
To: luca.boccassi@gmail.com
Cc: web@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-web] [PATCH 2/2] Update roadmap with projected 16.11.8 release date
Date: Thu, 14 Jun 2018 12:59:33 +0200 [thread overview]
Message-ID: <3437344.gYrXqH9cMy@xps> (raw)
In-Reply-To: <20180614101957.13889-2-luca.boccassi@gmail.com>
14/06/2018 12:19, luca.boccassi@gmail.com:
> From: Luca Boccassi <bluca@debian.org>
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
I think you can merge both patches with title "release 16.11.7".
So next time we will look at this patch and will remember
to update the roadmap at the same time.
next prev parent reply other threads:[~2018-06-14 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 10:19 [dpdk-web] [PATCH 1/2] Add 16.11.7 link and metadata to rel.html luca.boccassi
2018-06-14 10:19 ` [dpdk-web] [PATCH 2/2] Update roadmap with projected 16.11.8 release date luca.boccassi
2018-06-14 10:59 ` Thomas Monjalon [this message]
2018-06-14 11:05 ` Luca Boccassi
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=3437344.gYrXqH9cMy@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=luca.boccassi@gmail.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).