From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] MAINTAINERS: add keyword "tegra" to Tegra section
Date: Fri, 08 Feb 2013 20:15:56 -0700 [thread overview]
Message-ID: <5115BF6C.6050509@wwwdotorg.org> (raw)
In-Reply-To: <1360371906.13487.9.camel@joe-AO722>
On 02/08/2013 06:05 PM, Joe Perches wrote:
> On Fri, 2013-02-08 at 17:47 -0700, Stephen Warren wrote:
>> On 02/08/2013 05:40 PM, Joe Perches wrote:
>>> On Fri, 2013-02-08 at 13:04 -0700, Stephen Warren wrote:
>>>> (?<!in)tegra
>>>
>>> This doesn't work well. It matches too many
>>> words like integral.
>>
>> Hmmm. That's exactly what the (?<!in) negative look-behind assertion is
>> attempting to avoid. It works fine here. Is there some dependency on
>> Perl version or something? My Perl version is v5.14.2.
>
> Integral matches
>
> I don't see any issue with using a leading \b
Oh right, it's a capitalization issue; I only tested with "integral" not
"Integral".
The problem with \btegra is that it wouldn't match _tegra, which would
be useful. Perhaps a custom almost-equivalent (?i)[^a-z]tegra would work?
next prev parent reply other threads:[~2013-02-09 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 20:04 [PATCH] MAINTAINERS: add keyword "tegra" to Tegra section Stephen Warren
[not found] ` <1360353891-24210-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-09 0:40 ` Joe Perches
2013-02-09 0:47 ` Stephen Warren
2013-02-09 1:05 ` Joe Perches
2013-02-09 3:15 ` Stephen Warren [this message]
[not found] ` <5115BF6C.6050509-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-09 4:02 ` 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=5115BF6C.6050509@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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