[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2009291012560.2808@hadrien>
Date: Tue, 29 Sep 2020 10:18:14 +0200 (CEST)
From: Julia Lawall <julia.lawall@...ia.fr>
To: Joe Perches <joe@...ches.com>
cc: Julia Lawall <julia.lawall@...ia.fr>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] scripts/most_common_subject_prefix.pl: Find the most
common commit subject prefix
On Tue, 29 Sep 2020, Joe Perches wrote:
> On Tue, 2020-09-29 at 09:45 +0200, Julia Lawall wrote:
> > On Mon, 28 Sep 2020, Joe Perches wrote:
> > < This will emit a single line that is the most commonly used commit
> > > subject prefix up to and including the last colon of the commit subject
> > > for commits that _only_ include the specific file and not any other file.
> >
> > For the comma->semicolon patches, I noticed the need for a number of
> > suject lines of the form:
> >
> > hwrng: xxx - patch description
> >
> > So maybe other delimiters have to be taken into account.
>
> Maybe. Can you provide a few more examples?
Looking through git log --oneline, nothing else is jumping out. Another
issue is colons in the message text. I think that I check that the only
spaces have the form ": " to avoid this problem, but I do see:
88db0aa24216 all arch: remove system call sys_sysctl
92e4edba6e2 perf ftrace: Make option description initials all capital letters
(most of the perf patches seem to be like this one)
Here is another with -
27aced19e098 Input: exc3000 - add reset gpio support
Reverts seem to typically have Revert followed by the original subject
line in quotes.
julia
Powered by blists - more mailing lists