From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, stable@dpdk.org
Cc: yskoh@mellanox.com, christian.ehrhardt@canonical.com
Subject: Re: [dpdk-stable] [PATCH stable-scripts] README: General updates
Date: Fri, 05 Oct 2018 16:20:06 +0100 [thread overview]
Message-ID: <1538752806.8721.16.camel@debian.org> (raw)
In-Reply-To: <20181005151711.21130-1-ktraynor@redhat.com>
On Fri, 2018-10-05 at 16:17 +0100, Kevin Traynor wrote:
> - re-order 1-import into a more natural flow of sub-steps
> - add additional details about various steps
> - remove that typos should not be backported
> - few spelling/grammar fixes
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> README | 61 ++++++++++++++++++++++++++++++++++++++----------------
> -------
> 1 file changed, 38 insertions(+), 23 deletions(-)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-10-05 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 15:17 Kevin Traynor
2018-10-05 15:20 ` 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=1538752806.8721.16.camel@debian.org \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=stable@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).