From: "L. Alberto Giménez" <agimenez@sysvalve.es>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Florian Mickler <florian@mickler.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH] get_maintainer.pl: Add support to match arbitrary text
Date: Tue, 25 Jan 2011 01:25:55 +0100 [thread overview]
Message-ID: <20110125002555.GB13167@bart.evergreen.loc> (raw)
In-Reply-To: <1295913226.3101.60.camel@Joe-Laptop>
On Mon, Jan 24, 2011 at 03:53:46PM -0800, Joe Perches wrote:
> On Tue, 2011-01-25 at 00:32 +0100, L. Alberto Giménez wrote:
> > Extend the usage of the K section in the MAINTAINERS file to support matching
> > regular expressions with the content that precedes the patch (delimited by three
> > dashes "---").
> > + } elsif (not $in_patch and m/^---/) {
> > + # enter "patch area": keywords matched only on changed lines
> > + $in_patch = 1;
>
> Not all patches need or have ---
>
> This would be better as "^---$"
Hi Joe,
As I replied to you previously, please feel free to fix the patch. Most of the
patches I've seen use that line as a separator. Could you please give me the
right regexp to detect the beginning of patches?
On the other hand, if it's not properly detected, it will just match the "K"
keywords against all the patch lines (not just deleted or added lines). For a
standard unified diff format that would be 3 context lines that should match
with something like "^Subject: whatever". Again, it's just a proposal waiting
for comments/enhancements.
The idea here was to enable "triggers" in the subject to add the proper CCs. It
just ended up in a "match anything against the file content" change.
Regards,
--
L. Alberto Giménez
JabberID agimenez@jabber.sysvalve.es
GnuPG key ID 0x3BAABDE1
next prev parent reply other threads:[~2011-01-25 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:32 L. Alberto Giménez
2011-01-24 23:53 ` Joe Perches
2011-01-25 0:25 ` L. Alberto Giménez [this message]
2011-01-25 14:08 ` [PATCH] get_maintainer.pl: Allow "K:" pattern tests to match non-patch text Joe Perches
2011-01-25 18:44 ` L. Alberto Giménez
2011-01-25 18:58 ` Joe Perches
2011-01-26 12:23 ` "L. Alberto Giménez"
2011-01-25 14:23 ` [PATCH] get_maintainer.pl: Add support to match arbitrary text Joe Perches
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=20110125002555.GB13167@bart.evergreen.loc \
--to=agimenez@sysvalve.es \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=florian@mickler.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=w.sang@pengutronix.de \
/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®