From: Joe Perches <joe@perches.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Jingoo Han <jg1.han@samsung.com>,
'Ryan Mallon' <rmallon@gmail.com>,
'Florian Tobias Schandinat' <FlorianSchandinat@gmx.de>,
kernel-janitors@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH] drivers/video/ep93xx-fb.c: clean up error-handling code
Date: Tue, 24 Apr 2012 12:46:26 +0000 [thread overview]
Message-ID: <1335271586.25429.19.camel@joe2Laptop> (raw)
In-Reply-To: <alpine.DEB.2.02.1204190713200.1954@localhost6.localdomain6>
On Thu, 2012-04-19 at 07:14 +0200, Julia Lawall wrote:
> I don't know thw impact of the ./. I use the options
>
> --nokeywords --nogit-fallback --subsystem --norolestats -f
>
> julia
>
> On Thu, 19 Apr 2012, Jingoo Han wrote:
>
> >> -----Original Message-----
> >> From: Ryan Mallon
[]
> >> Oddly, scripts/get_maintainer.pl on this file doesn't return me, even
> >> though, according to git blame, I am the author of 90% of the commits.
> >> Should I have an entry in the MAINTAINERS file, or is
> >> scripts/get_maintainer.pl not working properly?
> >
> > There are optional differences in using scripts/get_maintainer.pl.
> > If you use './' ahead of file path, you will see your name.
> >
> > Without './' ahead of 'drivers/video/ep93xx-fb.c':
> > ./scripts/get_maintainer.pl --file drivers/video/ep93xx-fb.c
> > Florian Tobias Schandinat <FlorianSchandinat@gmx.de> (maintainer:FRAMEBUFFER LAYER)
> > linux-fbdev@vger.kernel.org (open list:FRAMEBUFFER LAYER)
> > linux-kernel@vger.kernel.org (open list)
> >
> > With './' ahead of 'drivers/video/ep93xx-fb.c':
> > ./scripts/get_maintainer.pl --file ./drivers/video/ep93xx-fb.c
> > Ryan Mallon <rmallon@gmail.com> (commit_signer:2/3g%)
> > Paul Gortmaker <paul.gortmaker@windriver.com> (commit_signer:1/33%)
> > H Hartley Sweeten <hsweeten@visionengravers.com> (commit_signer:1/33%)
> > Jesper Juhl <jj@chaosbits.net> (commit_signer:1/33%)
> > Jiri Kosina <jkosina@suse.cz> (commit_signer:1/33%)
> > linux-kernel@vger.kernel.org (open list)
Prefixing "./" to the file path bypasses the normal
get_maintainers pattern check for file maintainership.
Florian Schandinat and linux-fbdev are not returned
in the second lookup above.
One of the patterns for FRAMEBUFFER is
F: drivers/video/
which is a direct match for is ep93xx-fb.c file,
so --git is not used by default.
Adding --git may be appropriate and it also returns
Ryan's name in this case.
$ ./scripts/get_maintainer.pl -f drivers/video/ep93xx-fb.c
Florian Tobias Schandinat <FlorianSchandinat@gmx.de> (maintainer:FRAMEBUFFER LAYER)
linux-fbdev@vger.kernel.org (open list:FRAMEBUFFER LAYER)
linux-kernel@vger.kernel.org (open list)
$ ./scripts/get_maintainer.pl --git -f drivers/video/ep93xx-fb.c
Florian Tobias Schandinat <FlorianSchandinat@gmx.de> (maintainer:FRAMEBUFFER LAYER)
Ryan Mallon <rmallon@gmail.com> (commit_signer:2/3g%)
Paul Gortmaker <paul.gortmaker@windriver.com> (commit_signer:1/33%)
H Hartley Sweeten <hsweeten@visionengravers.com> (commit_signer:1/33%)
Jesper Juhl <jj@chaosbits.net> (commit_signer:1/33%)
Jiri Kosina <jkosina@suse.cz> (commit_signer:1/33%)
linux-fbdev@vger.kernel.org (open list:FRAMEBUFFER LAYER)
linux-kernel@vger.kernel.org (open list)
Nominally, as framebuffer maintainer, Florian
should also have "signed-off" on these commits,
but many subsystems don't actually have a
single path or person for patches and commits.
This file came into the tree via Andrew Morton.
Another way to investigate who actually does
work on an individual file is to use the
get_maintainer.pl option "--interactive".
That can give you an output like:
* # email/list and role:stats auth sign
* 1 Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
maintainer:FRAMEBUFFER LAYER
* 2 Ryan Mallon <rmallon@gmail.com> 4 4
commit_signer:2/3g%,authored lines:645/650™%,commits:4/8P%
* 3 Paul Gortmaker <paul.gortmaker@windriver.com> 1 1
commit_signer:1/33%,commits:1/8\x12%
* 4 H Hartley Sweeten <hsweeten@visionengravers.com> 0 2
commit_signer:1/33%,commits:2/8%%
* 5 Jesper Juhl <jj@chaosbits.net> 0 1
commit_signer:1/33%
* 6 Jiri Kosina <jkosina@suse.cz> 0 1
commit_signer:1/33%
* 7 Andrew Morton <akpm@linux-foundation.org> 0 2
commits:2/8%%
* 8 Russell King <rmk+kernel@arm.linux.org.uk> 0 1
commits:1/8\x12%
* 9 linux-fbdev@vger.kernel.org
open list:FRAMEBUFFER LAYER
* 10 linux-kernel@vger.kernel.org
open list
About maintainership for individual files:
If anyone thinks they are the maintainer for
a particular file, generally they should submit
a patch to MAINTAINERS adding a section with
their name, maintainership level and an
appropriate file pattern.
next prev parent reply other threads:[~2012-04-24 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 19:37 [PATCH] drivers/video/ep93xx-fb.c: clean up error-handling code Julia Lawall
2012-04-18 20:35 ` H Hartley Sweeten
2012-04-19 0:15 ` Ryan Mallon
2012-04-19 2:16 ` Jingoo Han
2012-04-19 5:14 ` Julia Lawall
2012-04-24 12:46 ` Joe Perches [this message]
2012-04-24 21:12 ` Ryan Mallon
2012-04-25 1:19 ` Jingoo Han
2012-04-23 6:19 ` Florian Tobias Schandinat
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=1335271586.25429.19.camel@joe2Laptop \
--to=joe@perches.com \
--cc=FlorianSchandinat@gmx.de \
--cc=jg1.han@samsung.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.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