From: Julia Lawall <julia.lawall@inria.fr>
To: Joe Perches <joe@perches.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] scripts/most_common_subject_prefix.pl: Find the most common commit subject prefix
Date: Tue, 29 Sep 2020 10:18:14 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2009291012560.2808@hadrien> (raw)
In-Reply-To: <c04c10773d5fd12fac67d0dc9ebab46d41962376.camel@perches.com>
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
prev parent reply other threads:[~2020-09-29 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 5:36 Joe Perches
2020-09-29 7:45 ` Julia Lawall
2020-09-29 8:08 ` Joe Perches
2020-09-29 8:18 ` Julia Lawall [this message]
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=alpine.DEB.2.22.394.2009291012560.2808@hadrien \
--to=julia.lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--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
all inboxes | Powered by JetHome®