From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, dev@openvswitch.org
Cc: stable@dpdk.org, christian.ehrhardt@canonical.com
Subject: Re: [dpdk-stable] [PATCH] doc: update stable section
Date: Mon, 22 Feb 2021 12:01:23 +0000 [thread overview]
Message-ID: <c2268deb879badfab63fc36ca13e330dcfaa39ef.camel@debian.org> (raw)
In-Reply-To: <20210219102313.413368-1-ktraynor@redhat.com>
On Fri, 2021-02-19 at 10:23 +0000, Kevin Traynor wrote:
> Updating the docs to elaborate on the stable release
> characteristics and better document the current practice
> about new features in stable releases.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 33 ++++++++++++++++++++++++------
> 1 file changed, 27 insertions(+), 6 deletions(-)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2021-02-22 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 10:23 Kevin Traynor
2021-02-22 12:01 ` 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=c2268deb879badfab63fc36ca13e330dcfaa39ef.camel@debian.org \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@openvswitch.org \
--cc=ktraynor@redhat.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).