[lkml]   [2018]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: Subsystem Profile
On Thu, 15 Nov 2018, Julia Lawall <> wrote:
> On Thu, 15 Nov 2018, Geert Uytterhoeven wrote:
>> Hi Julia,
>> On Thu, Nov 15, 2018 at 6:48 AM Julia Lawall <> wrote:
>> > How about patch subject lines? What is the formula that should be used to
>> > transform the name(s) of the affected file(s) into an appropriate suject
>> > line?
>> Automating that may be difficult.
>> I always use "git log --oneline", and try to derive something sane
>> from its output.
> Yes, I do likewise. But there may be some subsystems for which it would
> be possible to come up with a more specific policy. The advantage of what
> is proposed here is that it is not necessary to come up with a single
> formula that works everywhere. Even a description in English could be
> helpful.

I quickly cooked up this script to produce the top-5 commit prefixes for
the given files over the arbitrary last 200 commits. It'll give you a
pretty good idea if you're even close.

# usage: subject-prefix FILE [...]
# show top 5 subject prefixes for FILEs

git log --format=%s -n 200 -- "$@" |\
grep -v "^Merge " |\
sed 's/\(.*\):.*/\1/' |\
sort | uniq -c | sort -nr | sed 's/ *[0-9]\+ //' |\
head -n 5

Someone who knows perl could turn that into a checkpatch check: See if
the patch subject prefix is one of the top-5 for all files changed by
the patch, and ask the user to double check if it isn't. Or some
heuristics thereof.


Jani Nikula, Intel Open Source Graphics Center

 \ /
  Last update: 2018-11-16 13:44    [W:0.171 / U:0.704 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site