linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	"joe@perches.com" <joe@perches.com>
Cc: "andriy.shevchenko@intel.com" <andriy.shevchenko@intel.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"ardeleanalex@gmail.com" <ardeleanalex@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: Re: [PATCH] MAINTAINERS: remove Stefan Popa's email
Date: Sun, 22 Mar 2020 09:09:10 +0000	[thread overview]
Message-ID: <6175728c63483acc80cf36f40e17fa5bac18d545.camel@analog.com> (raw)
In-Reply-To: <CAHp75VcAo4qHvFyVkv3Keq63XD_HfSvJ=1LBbxYTM0kYGWJh_g@mail.gmail.com>

On Sat, 2020-03-21 at 22:18 +0200, Andy Shevchenko wrote:
> [External]
> 
> On Sat, Mar 21, 2020 at 10:11 PM Joe Perches <joe@perches.com> wrote:
> > On Sat, 2020-03-21 at 21:48 +0200, Andy Shevchenko wrote:
> > > On Tue, Mar 17, 2020 at 04:33:36PM +0200, Alexandru Ardelean wrote:
> > > > The email is no longer active. This change removes Stefan's email from
> > > > the
> > > > MAINTAINERS list and replaces it with Michael Hennerich's.
> > > > 
> > > 
> > > Are you planning to fix entries as parse-maintainers.pl does?
> > > (Maybe in a separate change, but also why not here)
> > 
> > I think perhaps you should not ask people to use parse-maintainers
> > on specific sections anymore as it's rather confusing to use and
> > it's best done as a one-shot by Linus one day.  I hope soon.
> 
> Why not? The benefits are
>  - people will know about the tool
>  - the particular sections will be fixed since they are touching the data base
> 
> And it doesn't prevent Linus or anybody to run the script in the future.
> 
> Actually it will teach people ahead to use the tool then in the future
> we won't see such drastic deviation in ordering.
> 

i guess this means it's a noop for me now

      reply	other threads:[~2020-03-22  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 14:33 [PATCH] MAINTAINERS: remove Stefan Popa's email Alexandru Ardelean
2020-03-21  9:04 ` [PATCH v2] " Alexandru Ardelean
2020-03-21 16:46   ` Jonathan Cameron
2020-03-21 19:48 ` [PATCH] " Andy Shevchenko
2020-03-21 20:09   ` Joe Perches
2020-03-21 20:18     ` Andy Shevchenko
2020-03-22  9:09       ` Ardelean, Alexandru [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=6175728c63483acc80cf36f40e17fa5bac18d545.camel@analog.com \
    --to=alexandru.ardelean@analog.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=ardeleanalex@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).