From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Luca Boccassi <bluca@debian.org>,
nhorman@tuxdriver.com
Subject: Re: [PATCH] doc: move and update experimental API description
Date: Thu, 09 Aug 2018 18:36:14 +0200 [thread overview]
Message-ID: <10239261.CnNu2H3yVC@xps> (raw)
In-Reply-To: <9dc0462f-4254-4267-e464-3b51a6d2e252@intel.com>
25/05/2018 17:37, Ferruh Yigit:
> On 5/25/2018 1:22 PM, Luca Boccassi wrote:
> > On Fri, 2018-05-25 at 17:37 +0530, Shreyansh Jain wrote:
> >> Experimental API text has been moved into a sub-section of ABI
> >> Policy.
> >> A paragraph has been added to explain the process for removal of an
> >> experimental tag.
> >>
> >> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> >>
> >> ---
> >> note:
> >> The movement of text into a sub-section is relevant as the previous
> >> position
> >> was in middle of a continuous text explaining ABI policy - whereas,
> >> experimental is not truly an ABI policy.
> >> No change to the original text has been made, except appending a new
> >> paragraph. Though, this does spoil the blame/praise.
> >>
> >> doc/guides/contributing/versioning.rst | 54 +++++++++++++++---------
> >> --
> >> 1 file changed, 31 insertions(+), 23 deletions(-)
> >
> > Acked-by: Luca Boccassi <bluca@debian.org>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
prev parent reply other threads:[~2018-08-09 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 12:07 [PATCH] doc: move and update experimental API description Shreyansh Jain
2018-05-25 12:22 ` Luca Boccassi
2018-05-25 15:37 ` Ferruh Yigit
2018-08-09 16:36 ` Thomas Monjalon [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=10239261.CnNu2H3yVC@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=shreyansh.jain@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.