From: Joe Perches <joe@perches.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Anton Vorontsov <anton.vorontsov@linaro.org>,
Michal Hocko <mhocko@suse.cz>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [bug] get_maintainer.pl incomplete output
Date: Wed, 16 Oct 2013 21:36:25 -0700 [thread overview]
Message-ID: <1381984585.22110.92.camel@joe-AO722> (raw)
In-Reply-To: <alpine.DEB.2.02.1310162117140.2453@chino.kir.corp.google.com>
On Wed, 2013-10-16 at 21:19 -0700, David Rientjes wrote:
> On Wed, 16 Oct 2013, Joe Perches wrote:
>
> > > I haven't looked closely at scripts/get_maintainer.pl, but I recently
> > > wrote a patch touching mm/vmpressure.c and it doesn't list the file's
> > > author, Anton Vorontsov <anton.vorontsov@linaro.org>.
> > >
> > > Even when I do scripts/get_maintainer.pl -f mm/vmpressure.c, his entry is
> > > missing and git blame attributs >90% of the lines to his authorship.
> > >
> > > $ ./scripts/get_maintainer.pl -f mm/vmpressure.c
> > > Tejun Heo <tj@kernel.org> (commit_signer:6/7=86%)
> > > Michal Hocko <mhocko@suse.cz> (commit_signer:5/7=71%)
> > > Andrew Morton <akpm@linux-foundation.org> (commit_signer:4/7=57%)
> > > Li Zefan <lizefan@huawei.com> (commit_signer:3/7=43%)
> > > "Kirill A. Shutemov" <kirill@shutemov.name> (commit_signer:1/7=14%)
> > > linux-mm@kvack.org (open list:MEMORY MANAGEMENT)
> > > linux-kernel@vger.kernel.org (open list)
> > >
> > > Any ideas?
> >
> > get_maintainer has a lot of options.
> >
> > get_maintainer tries to find people that are either
> > listed in the MAINTAINERS file or that have recently
> > (in the last year by default) worked on the file.
> >
> > If you want to find all authors, use the --git-blame option
> >
> > It's not the default because it can take quite awhile to run.
> >
>
> Hmm, it's a little strange to only consider recent activity when >90% of
> the lines were written by someone not listed. Isn't there any faster way
> to determine that besides using the expensive git blame?
Not so far as I know.
> Something like
> weighing the output of "git show --shortstat" for all commits in "git log
> mm/vmpressure.c" to determine the most important recent changes? That
> should be fairly cheap.
Important can be hard to determine.
git blame effectively does a --follow
get_maintainers already does a git log <file>
and accumulates all the signatures for the
time selected by --git-since
It doesn't weight each commit by +/- count.
I think the most significant negative to
the current get_maintainer is that only the
"signature" lines are considered.
The "Author:" line isn't.
The default ris for get_maintainer to only list
a maximum of 5 "maintainers" ordered by signature
count.
Anton has only signed/acked 1.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-10-17 4:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 0:43 [patch] mm, vmpressure: add high level David Rientjes
2013-10-17 3:05 ` Anton Vorontsov
2013-10-17 3:44 ` David Rientjes
2013-10-17 3:51 ` [bug] get_maintainer.pl incomplete output David Rientjes
2013-10-17 4:03 ` Joe Perches
2013-10-17 4:19 ` David Rientjes
2013-10-17 4:36 ` Joe Perches [this message]
2013-10-17 19:12 ` Andrew Morton
2013-10-17 19:23 ` Joe Perches
2013-10-18 4:17 ` Joe Perches
2013-10-18 22:58 ` David Rientjes
2013-10-19 0:25 ` Joe Perches
2013-11-14 21:56 ` [PATCH] get_maintainer: Add commit author information to --rolestats Joe Perches
2013-11-15 2:16 ` Chen Gang
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=1381984585.22110.92.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=anton.vorontsov@linaro.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).