From: Thomas Monjalon <thomas@monjalon.net>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: dev@dpdk.org, stephen@networkplumber.org,
bruce.richardson@intel.com, ferruh.yigit@intel.com,
konstantin.ananyev@intel.com, jerinj@marvell.com,
olivier.matz@6wind.com, nhorman@tuxdriver.com,
maxime.coquelin@redhat.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, hemant.agrawal@nxp.com,
ktraynor@redhat.com, aconole@redhat.com
Subject: Re: [dpdk-dev] [PATCH v11 0/3] doc: changes to abi policy introducing major abi versions
Date: Tue, 12 Nov 2019 08:55:15 +0100 [thread overview]
Message-ID: <8694519.e3y6Jp8dpY@xps> (raw)
In-Reply-To: <1573473478-8669-1-git-send-email-mdr@ashroe.eu>
11/11/2019 12:57, Ray Kinsella:
> TL;DR abbreviation:
> A major ABI version that all DPDK releases during an agreed period support. ABI
> versioning is managed at a project-level, in place of library-level management.
> ABI changes to add new features are permitted, as long as ABI compatibility with
> the major ABI version is maintained.
>
[...]
> Ray Kinsella (3):
> doc: separate versioning.rst into version and policy
> doc: changes to abi policy introducing major abi versions
> doc: updates to versioning guide for abi versions
Applied, thanks
next prev parent reply other threads:[~2019-11-12 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 12:46 [dpdk-dev] [PATCH v9 0/4] " Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 1/4] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 2/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-08 17:11 ` Thomas Monjalon
2019-11-08 17:12 ` Ray Kinsella
2019-11-08 17:38 ` Thomas Monjalon
2019-11-11 11:03 ` Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 3/4] doc: updates to versioning guide for " Ray Kinsella
2019-11-08 12:46 ` [dpdk-dev] [PATCH v9 4/4] doc: add maintainer for abi policy Ray Kinsella
2019-11-08 17:18 ` Thomas Monjalon
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 0/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 1/3] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 2/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 10:37 ` [dpdk-dev] [PATCH v10 3/3] doc: updates to versioning guide for " Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 0/3] doc: changes to abi policy introducing major " Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 1/3] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 2/3] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-11 11:57 ` [dpdk-dev] [PATCH v11 3/3] doc: updates to versioning guide for " Ray Kinsella
2019-11-12 7:55 ` Thomas Monjalon [this message]
2019-11-12 8:49 ` [dpdk-dev] [PATCH v11 0/3] doc: changes to abi policy introducing major " Ray Kinsella
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=8694519.e3y6Jp8dpY@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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).