ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	ksummit@lists.linux.dev
Subject: Re: Validating MAINTAINERS entries?
Date: Wed, 10 Aug 2022 12:10:00 +0300	[thread overview]
Message-ID: <20220810091000.GR3460@kadam> (raw)
In-Reply-To: <CAKXUXMwOAuqD=o1ryZP4oq2dLvTi+7iwQc6gfBF2DiU+_7NH9A@mail.gmail.com>

On Wed, Aug 10, 2022 at 10:55:44AM +0200, Lukas Bulwahn wrote:
> On Wed, Aug 10, 2022 at 10:50 AM Greg KH <greg@kroah.com> wrote:
> >
> > On Wed, Aug 10, 2022 at 11:26:40AM +0300, Dan Carpenter wrote:
> > > On Tue, Aug 09, 2022 at 05:13:16PM -0700, Stephen Hemminger wrote:
> > > > Several times in the past, when using MAINTAINERS list either automatically
> > > > (or from manual entry) have found the mailing address in the file is no longer valid.
> > > >
> > > > What about doing an annual probe mail to all maintainers and sending
> > > > a patch to prune out any addresses that auto respond as dead.
> > > > This won't catch ghost entries but would find any dead ones.
> > > >
> > >
> > > Also we could add a RETIRED file or something for when people retire and
> > > don't want get_maintainer.pl hassling them.
> >
> > Isn't that what CREDITS is for?
> >
> 
> I agree with Greg here.
> 
> For:
> "a RETIRED file or something for when people retire" -> CREDITS
> "don't want get_maintainer.pl hassling them" -> .get_maintainer.ignore
> 
> Choose what fits for your case.

Perfect!  Thanks.  I had no idea about .get_maintainer.ignore and
started to implement it myself, but it turns out I am lazy and suck at
Perl.

regards,
dan carpenter


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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  0:13 Stephen Hemminger
2022-08-10  8:23 ` Greg KH
2022-08-10  8:26 ` Dan Carpenter
2022-08-10  8:36   ` Greg KH
2022-08-10  8:55     ` Lukas Bulwahn
2022-08-10  9:10       ` Dan Carpenter [this message]
2022-08-10 11:50       ` Lee Jones
2022-08-10 12:04         ` Dan Carpenter
2022-08-10 12:12           ` Serge E. Hallyn
2022-08-10 12:50           ` Mark Brown
2022-08-10 13:25             ` Lee Jones
2022-08-10 13:54               ` Rob Herring
2022-08-10 14:01                 ` Mark Brown
2022-08-10 14:19                   ` Konstantin Ryabitsev
2022-08-10 14:20                   ` Rob Herring
2022-08-10 14:35                     ` Mark Brown
2022-08-11 12:36                       ` Sudip Mukherjee
2022-08-10 15:29                 ` Lee Jones
2022-08-11  8:35             ` Geert Uytterhoeven
2022-08-11  8:42               ` Christoph Hellwig
2022-08-10  8:46   ` Lukas Bulwahn
2022-08-10  8:42 ` Lukas Bulwahn

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=20220810091000.GR3460@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=greg@kroah.com \
    --cc=ksummit@lists.linux.dev \
    --cc=lukas.bulwahn@gmail.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