From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
Andy Whitcroft <apw@canonical.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Adjust regular expressions in $logFunctions
Date: Tue, 09 May 2017 20:52:34 +0000 [thread overview]
Message-ID: <1494363154.20782.7.camel@perches.com> (raw)
In-Reply-To: <a2178c87-9229-978d-c94e-6c124755c440@users.sourceforge.net>
On Tue, 2017-05-09 at 21:00 +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 9 May 2017 20:40:51 +0200
>
> * Two alternations contained an empty element. Use the question mark
> metacharacter instead to express optional items in the search pattern.
>
> * Some alternation elements shared a common prefix (like an underscore).
> Improve the specification of this detail by more non-capturing groups.
No thanks. Perl is odd enough already adding more non-capture
groups when the arguments are clearly specified is harder to read.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
Andy Whitcroft <apw@canonical.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Adjust regular expressions in $logFunctions
Date: Tue, 09 May 2017 13:52:34 -0700 [thread overview]
Message-ID: <1494363154.20782.7.camel@perches.com> (raw)
In-Reply-To: <a2178c87-9229-978d-c94e-6c124755c440@users.sourceforge.net>
On Tue, 2017-05-09 at 21:00 +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 9 May 2017 20:40:51 +0200
>
> * Two alternations contained an empty element. Use the question mark
> metacharacter instead to express optional items in the search pattern.
>
> * Some alternation elements shared a common prefix (like an underscore).
> Improve the specification of this detail by more non-capturing groups.
No thanks. Perl is odd enough already adding more non-capture
groups when the arguments are clearly specified is harder to read.
next prev parent reply other threads:[~2017-05-09 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:00 [PATCH] checkpatch: Adjust regular expressions in $logFunctions SF Markus Elfring
2017-05-09 19:00 ` SF Markus Elfring
2017-05-09 20:52 ` Joe Perches [this message]
2017-05-09 20:52 ` Joe Perches
2017-05-09 21:01 ` SF Markus Elfring
2017-05-09 21:01 ` SF Markus Elfring
2017-05-09 21:16 ` Joe Perches
2017-05-09 21:16 ` 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=1494363154.20782.7.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.