From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, web@dpdk.org
Cc: thomas@monjalon.net, yskoh@mellanox.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-web] [PATCH] release 18.11.2
Date: Tue, 11 Jun 2019 19:26:36 +0100 [thread overview]
Message-ID: <2b50046b0e2c4ef9d826269aa7d19cd8e57067bc.camel@debian.org> (raw)
In-Reply-To: <20190611182019.22591-1-ktraynor@redhat.com>
On Tue, 2019-06-11 at 19:20 +0100, Kevin Traynor wrote:
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> content/download/_index.md | 6 +++---
> content/roadmap/_index.md | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-06-11 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:20 Kevin Traynor
2019-06-11 18:26 ` Luca Boccassi [this message]
2019-06-11 18:47 ` Kevin Traynor
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=2b50046b0e2c4ef9d826269aa7d19cd8e57067bc.camel@debian.org \
--to=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yskoh@mellanox.com \
/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).