From: Joe Perches <joe@perches.com>
To: Claudio Fontana <cfontana@suse.de>, Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: in_commit_log: is the wrong token being matched for the MAINTAINERS need updating message?
Date: Mon, 10 Aug 2020 09:59:19 -0700 [thread overview]
Message-ID: <17256c5e44cf5489d6eb1505077edc0910e9f3b8.camel@perches.com> (raw)
In-Reply-To: <540c6741-3f22-ec85-0a14-3165115430df@suse.de>
On Mon, 2020-08-10 at 18:45 +0200, Claudio Fontana wrote:
> We can see that in the sample patch input we are matching the line
>
> sound/{ => ac97}/ac97_bus.c | 0
>
> with the regex ($line =~ /\{\s*([\w\/\.\-]*)\s*\=\>\s*([\w\/\.\-]*)\s*\}/
>
> Is this actually wanted?
Yes, If this line is found, it's not intended to
be part of a commit message.
prev parent reply other threads:[~2020-08-10 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 16:45 Claudio Fontana
2020-08-10 16:59 ` Joe Perches [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=17256c5e44cf5489d6eb1505077edc0910e9f3b8.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=cfontana@suse.de \
--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®