DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
	david.marchand@redhat.com, ferruh.yigit@xilinx.com,
	mdr@ashroe.eu
Subject: [PATCH 0/1] update abi maintainership
Date: Mon,  8 Aug 2022 10:58:33 +0000	[thread overview]
Message-ID: <20220808105834.2826-1-mdr@ashroe.eu> (raw)

In anticipation of a role change. I wanted to make sure there is orderly handover of maintainership
of the abi. I think the proposed change reflects the reality of what is happening in the project in
anycase.

Ray Kinsella (1):
  devtools: eol abi as a separate function

 MAINTAINERS | 27 +++++++++------------------
 1 file changed, 9 insertions(+), 18 deletions(-)

--
2.20.1

             reply	other threads:[~2022-08-08 10:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 10:58 Ray Kinsella [this message]
2022-08-08 10:58 ` [PATCH 1/1] devtools: eol abi as a separate function Ray Kinsella
2022-10-11  0:36   ` 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=20220808105834.2826-1-mdr@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.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).