From: Kevin Traynor <ktraynor@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: Luca Boccassi <bluca@debian.org>,
Yongseok Koh <yskoh@mellanox.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH v4 1/3] doc: clean ABI/API policy guide
Date: Thu, 31 Jan 2019 17:46:14 +0000 [thread overview]
Message-ID: <314a042b-e1bd-eaa1-a4e4-4ff40b6cadd8@redhat.com> (raw)
In-Reply-To: <20190124181019.17168-1-ferruh.yigit@intel.com>
On 01/24/2019 06:10 PM, Ferruh Yigit wrote:
> The original document written from the point of ABI versioning but later
> additions make document confusing, convert document into a ABI/API
> policy documentation and organize the document in subsections:
> - ABI/API Deprecation
> - Experimental APIs
> - Library versioning
> - ABI versioning
>
> Aim to clarify confusion between deprecation versioned ABI and overall
> ABI/API deprecation, also ABI versioning and Library versioning by
> organizing the sections.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
For series
Acked-by: Kevin Traynor <ktraynor@redhat.com>
next prev parent reply other threads:[~2019-01-31 17:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 12:52 [RFC 1/2] doc: clean ABI/API policy guide Ferruh Yigit
2018-12-19 12:52 ` [RFC 2/2] doc: add deprecation marker usage Ferruh Yigit
2018-12-20 8:02 ` Luca Boccassi
2018-12-21 15:52 ` Ferruh Yigit
2018-12-20 8:02 ` [RFC 1/2] doc: clean ABI/API policy guide Luca Boccassi
2018-12-20 8:03 ` Luca Boccassi
2018-12-21 15:57 ` [PATCH v2 " Ferruh Yigit
2018-12-21 15:57 ` [PATCH v2 2/2] doc: add deprecation marker usage Ferruh Yigit
2019-01-22 16:23 ` [PATCH v3 1/3] doc: clean ABI/API policy guide Ferruh Yigit
2019-01-22 16:23 ` [PATCH v3 2/3] doc: make RTE_NEXT_ABI optional Ferruh Yigit
2019-01-22 16:23 ` [PATCH v3 3/3] doc: add deprecation marker usage Ferruh Yigit
2019-01-23 23:07 ` Kevin Traynor
2019-01-24 14:31 ` Ferruh Yigit
2019-01-24 15:33 ` Kevin Traynor
2019-01-24 16:29 ` Ferruh Yigit
2019-01-23 8:13 ` [PATCH v3 1/3] doc: clean ABI/API policy guide Neil Horman
2019-01-24 18:10 ` [PATCH v4 " Ferruh Yigit
2019-01-24 18:10 ` [PATCH v4 2/3] doc: make RTE_NEXT_ABI optional Ferruh Yigit
2019-01-31 17:18 ` Thomas Monjalon
2019-01-24 18:10 ` [PATCH v4 3/3] doc: add deprecation marker usage Ferruh Yigit
2019-01-31 17:17 ` Thomas Monjalon
2019-02-01 17:06 ` Ferruh Yigit
2019-03-01 16:46 ` Thomas Monjalon
2019-01-31 17:46 ` Kevin Traynor [this message]
2019-03-01 17:32 ` [PATCH v5 1/3] doc: clean ABI/API policy guide Ferruh Yigit
2019-03-01 17:32 ` [PATCH v5 2/3] doc: make RTE_NEXT_ABI optional Ferruh Yigit
2019-03-01 17:32 ` [PATCH v5 3/3] doc: add deprecation marker usage Ferruh Yigit
2019-03-01 17:40 ` Kevin Traynor
2019-03-27 13:29 ` Thomas Monjalon
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=314a042b-e1bd-eaa1-a4e4-4ff40b6cadd8@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--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 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.