From: Joe Perches <joe@perches.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org, jtoppins@redhat.com
Subject: Re: [PATCH] get_maintainer.pl: Add optional .get_maintainer.MAINTAINERS override
Date: Fri, 06 Jul 2018 11:31:13 -0700 [thread overview]
Message-ID: <c187fe5040cb616292dab6c106352273df95bc41.camel@perches.com> (raw)
In-Reply-To: <20180706175419.6irtvs64e6dbz7hk@redhat.com>
On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
> On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
> > On Tue, 2018-06-26 at 14:25 -0400, Prarit Bhargava wrote:
> > > OSes have additional maintainers that should be cc'd on patches or may
> > > want to circulate internal patches.
> > >
> > > Parse the .get_maintainer.MAINTAINERS file. Entries in the file
> > > can begin with a '+' to indicate the email and list entries should be
> > > added to the exiting MAINTAINERS output, or a '-' to indicate that the
> > > entries should override the existing MAINTAINERS file.
> > >
> > > Also add a help entry for the .get_maintainers.ignore file.
> >
> > I see no reason for this patch to be applied.
> > Why should it?
> > Why shouldn't this be in your private repository?
>
> Hi Joe,
>
> Would you be open to a '--mfile=<path>/MAINTAINERS' option that would
> override the default ./MAINTAINERS file? Then we could just add that to our
> .get_maintainers.conf file.
Hi Don.
Sure.
And that kinda already exists in mainline with
--find-maintainer-files where any subdirectory
that contains a MAINTAINER file is also read.
> Just trying to find ways to minimize our collection of private patches.
Perhaps that could be extended for your purpose
with some additional argument like a specific
optional directory/path where every subdirectory
would be found.
> Cheers,
> Don
cheers back, Joe
> > > + $line =~ s/\s*\n?$//;
> > > + push(@mfiles, $line);
> > > + }
> > > + close($conffile);
> > > + if ($add eq 0) {
> > > + foreach my $file (@mfiles) {
> > > + read_maintainer_file("$file");
> > > + }
> > > + return;
> > > + }
> > > + }
> > > +
> > > if (-d "${lk_path}MAINTAINERS") {
> > > opendir(DIR, "${lk_path}MAINTAINERS") or die $!;
> > > my @files = readdir(DIR);
> > > @@ -1068,6 +1094,14 @@ Notes:
> > > Entries in this file can be any command line argument.
> > > This file is prepended to any additional command line arguments.
> > > Multiple lines and # comments are allowed.
> > > + File ".get_maintainer.ignore", if it exists in the linux kernel source root
> > > + directory, can contain a list of email addresses to ignore. Multiple
> > > + lines and # comments are allowed.
> > > + File ".get_maintainer.MAINTAINERS", if it exists in the linux kernel source
> > > + root directory, can change the location of the MAINTAINERS file.
> > > + Entries beginning with a '+' are added to the default list, and
> > > + entries beginning with a '-' override the existing MAINTAINERS list
> > > + lookup. Multiple lines and # comments are allowed.
> > > Most options have both positive and negative forms.
> > > The negative forms for --<foo> are --no<foo> and --no-<foo>.
> > >
next prev parent reply other threads:[~2018-07-06 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 18:25 Prarit Bhargava
2018-06-26 20:16 ` Joe Perches
2018-06-26 22:52 ` Prarit Bhargava
2018-06-26 23:04 ` Joe Perches
2018-06-26 23:29 ` Prarit Bhargava
2018-07-06 17:54 ` Don Zickus
2018-07-06 18:31 ` Joe Perches [this message]
2018-07-06 18:44 ` Don Zickus
2018-07-06 19:39 ` Prarit Bhargava
2018-07-06 21:36 ` Joe Perches
2018-07-06 21:58 ` Don Zickus
2018-07-06 22:09 ` Joe Perches
2018-07-06 22:12 ` Don Zickus
2018-07-06 22:14 ` Joe Perches
2018-07-06 22:30 ` Don Zickus
2018-07-06 22:32 ` Don Zickus
2018-07-13 18:51 ` Don Zickus
2018-07-14 0:11 ` Joe Perches
2018-07-16 21:20 ` Don Zickus
2018-07-30 18:48 ` Don Zickus
2018-07-06 19:47 ` Don Zickus
2018-08-04 1:11 ` [PATCH] get_maintainer.pl: Add -mpath=<path or file> for MAINTAINERS file location Joe Perches
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=c187fe5040cb616292dab6c106352273df95bc41.camel@perches.com \
--to=joe@perches.com \
--cc=dzickus@redhat.com \
--cc=jtoppins@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
/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
all inboxes | Powered by JetHome®