DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: dev@dpdk.org, thomas@monjalon.net, 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 v8 1/4] doc: separate versioning.rst into version and policy
Date: Tue, 5 Nov 2019 09:37:23 -0800	[thread overview]
Message-ID: <20191105093723.5a7b818e@hermes.lan> (raw)
In-Reply-To: <1572967458-16487-2-git-send-email-mdr@ashroe.eu>

On Tue,  5 Nov 2019 15:24:15 +0000
Ray Kinsella <mdr@ashroe.eu> wrote:

> Separate versioning.rst into abi versioning and abi policy guidance, in
> preparation for adding more detail to the abi policy.
> 
> Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
> ---
>  doc/guides/contributing/abi_policy.rst     | 167 ++++++++
>  doc/guides/contributing/abi_versioning.rst | 427 +++++++++++++++++++++
>  doc/guides/contributing/index.rst          |   3 +-
>  doc/guides/contributing/patches.rst        |   2 +-
>  doc/guides/contributing/versioning.rst     | 591 -----------------------------
>  doc/guides/rel_notes/deprecation.rst       |   2 +-
>  6 files changed, 598 insertions(+), 594 deletions(-)
>  create mode 100644 doc/guides/contributing/abi_policy.rst
>  create mode 100644 doc/guides/contributing/abi_versioning.rst
>  delete mode 100644 doc/guides/contributing/versioning.rst
> 

Acked-by: Stephen Hemminger <stephen@networkplumber.og>

  reply	other threads:[~2019-11-05 17:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 15:24 [dpdk-dev] [PATCH v8 0/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 1/4] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-05 17:37   ` Stephen Hemminger [this message]
2019-11-06 16:11   ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 2/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-05 17:37   ` Stephen Hemminger
2019-11-06  0:11   ` Thomas Monjalon
2019-11-06  8:49     ` Ray Kinsella
2019-11-06  9:06       ` Thomas Monjalon
2019-11-06  9:21         ` David Marchand
2019-11-06  9:22         ` Ray Kinsella
2019-11-06 21:07           ` Thomas Monjalon
2019-11-08 14:09             ` Ray Kinsella
2019-11-06 16:12   ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 3/4] doc: updates to versioning guide for " Ray Kinsella
2019-11-05 17:37   ` Stephen Hemminger
2019-11-06 16:13   ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 4/4] doc: add maintainer for abi policy Ray Kinsella
2019-11-06 16:13   ` Mcnamara, John

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=20191105093723.5a7b818e@hermes.lan \
    --to=stephen@networkplumber.org \
    --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=thomas@monjalon.net \
    /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).