From: Olivier Matz <olivier.matz@6wind.com>
To: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] maintainers: remove olivier.matz@6wind.com
Date: Tue, 17 Oct 2023 21:32:37 +0200 [thread overview]
Message-ID: <ZS7hVTJFO5xPMbe7@platinum> (raw)
In-Reply-To: <b46fddd822924ebd8a1e8c45d69f76a8@huawei.com>
Hello,
On Tue, Oct 17, 2023 at 04:35:50PM +0000, Konstantin Ananyev wrote:
>
> > >
> > > > On Tue, Oct 17, 2023 at 04:27:37PM +0200, Olivier Matz wrote:
> > > > > Unfortunatly I don't have enough time to undertake my maintainer role at
> > > > > the expected level. It will probably not going to get better anytime
> > > > > soon, so remove myself from maintainers.
> > > > >
> > > > > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> > > > > ---
> > > > Sorry to see your name dropped from the file after so many years!
> > > >
> > > > Sadly,
> > > > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> > >
> > > Sorry to see you go.
> >
> > Echo the same here.
> >
> > > Should start a CREDITS file to remember past maintainers?
> >
> > +1
>
> +1 for both.
Thank you very much for your kind reactions.
About the CREDITS file, many people would deserve to have their name in
such a file. We already have the git history and the mail history, which
are forever engraved in the marble of the Internet :)
And... I'm not leaving the DPDK community, I'll definitely find some
time for a few reviews. I just want to have the MAINTAINERS file
reflecting the reality.
Olivier
prev parent reply other threads:[~2023-10-17 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 14:27 Olivier Matz
2023-10-17 15:32 ` Bruce Richardson
2023-10-17 16:00 ` Stephen Hemminger
2023-10-17 16:06 ` Jerin Jacob
2023-10-17 16:35 ` Konstantin Ananyev
2023-10-17 19:22 ` Thomas Monjalon
2023-10-17 19:32 ` Olivier Matz [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=ZS7hVTJFO5xPMbe7@platinum \
--to=olivier.matz@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@huawei.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).