From: Joe Perches <joe@perches.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Lee Jones <lee.jones@linaro.org>, "Theodore Ts'o" <tytso@mit.edu>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Laura Abbott <labbott@redhat.com>,
linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default
Date: Tue, 27 Oct 2015 10:49:35 -0700 [thread overview]
Message-ID: <1445968175.2757.14.camel@perches.com> (raw)
In-Reply-To: <20151027102950.GB3405@katana>
On Tue, 2015-10-27 at 11:29 +0100, Wolfram Sang wrote:
> > act as reviewers, they should have a mention in MAINTAINERS for
> > get_maintiner.pl to pull information from:
> >
> > R: Designated reviewer: FullName <address@domain>
> > These reviewers should be CCed on patches.
>
> I think this should do.
>
> Interested parties should start by scanning the mailing list :)
I think the concept of reviewers is fine.
A couple weeks ago, I suggested a mechanism to have reviewers
concentrate their entries into separate REVIEWERS file(s)
https://lkml.org/lkml/2015/10/16/649
These REVIEWERS* files would also work for companies that have
people with specific areas of expertise that want internal review
before public exposure.
Kconfig and Makefile files in directories like drivers/i2c/busses
are outliers because all new individual drivers are added to both
files.
The mechanism to limit git-fallback use is a directory depth match.
Wolfram has a MAINTAINERS entry of:
F: drivers/i2c/
but that doesn't pattern doesn't match the directory depth of
file drivers/i2c/busses/Kconfig so git-fallback is used for files
that don't have specific MAINTAINERS.
It _might_ make some sense to limit activation of git history in
that specific case, but for some path like arch/, that limitation
might _not_ make sense.
next prev parent reply other threads:[~2015-10-27 17:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 22:11 [PATCH] get_maintainer: Don't fallback to git by default Javier Martinez Canillas
2015-10-26 23:00 ` Laura Abbott
2015-10-27 0:08 ` Javier Martinez Canillas
2015-10-27 2:47 ` Theodore Ts'o
2015-10-27 4:57 ` joe
2015-10-27 5:03 ` Laura Abbott
2015-10-27 8:21 ` Lee Jones
2015-10-27 9:24 ` Wolfram Sang
2015-10-27 10:10 ` Lee Jones
2015-10-27 10:29 ` Wolfram Sang
2015-10-27 17:49 ` Joe Perches [this message]
2015-10-27 18:21 ` Joe Perches
2015-10-27 23:25 ` Wolfram Sang
2015-10-27 23:37 ` Joe Perches
2015-10-28 0:05 ` Wolfram Sang
2015-10-28 0:14 ` Joe Perches
2015-10-28 8:50 ` Lee Jones
2015-10-27 17:53 ` Joe Perches
2015-10-27 18:09 ` Lee Jones
2015-10-27 19:24 ` Javier Martinez Canillas
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=1445968175.2757.14.camel@perches.com \
--to=joe@perches.com \
--cc=javier@osg.samsung.com \
--cc=labbott@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.