From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/2] README: add some lessons learned from using the stable scripts
Date: Mon, 30 Jul 2018 17:29:19 +0100 [thread overview]
Message-ID: <1532968159.20916.45.camel@debian.org> (raw)
In-Reply-To: <20180730162447.17661-1-christian.ehrhardt@canonical.com>
On Mon, 2018-07-30 at 18:24 +0200, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> README | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-07-30 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:24 Christian Ehrhardt
2018-07-30 16:24 ` [dpdk-stable] [PATCH 2/2] import: fix duplicate subject lines Christian Ehrhardt
2018-07-30 16:29 ` Luca Boccassi
2018-07-30 16:29 ` Luca Boccassi [this message]
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=1532968159.20916.45.camel@debian.org \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@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).