From: Ryan Mallon <rmallon@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Jingoo Han <jg1.han@samsung.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 21:12:28 +0000 [thread overview]
Message-ID: <4F97173C.5010808@gmail.com> (raw)
In-Reply-To: <1335271586.25429.19.camel@joe2Laptop>
On 24/04/12 22:46, Joe Perches wrote:
> 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.
Hi Joe,
Thanks for the info.
> 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.
>
The original driver was written before Florian became the
framebuffer maintainer. The subsystem had no real maintainer
at the time, which is why it went via Andrew.
> 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.
Hmm, perhaps author is a better term than maintainer here. Any
patches should still go via the framebuffer maintainer, Florian,
but it would be useful in many cases for the original and/or
most regular commit author to also get Cc'ed since in many
cases they will have a better understanding of the code, even
if the aren't "maintaining" it.
~Ryan
next prev parent reply other threads:[~2012-04-24 21:12 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
2012-04-24 21:12 ` Ryan Mallon [this message]
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=4F97173C.5010808@gmail.com \
--to=rmallon@gmail.com \
--cc=FlorianSchandinat@gmx.de \
--cc=jg1.han@samsung.com \
--cc=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).