From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: checkpatch: Adjust regular expressions in $logFunctions
Date: Tue, 09 May 2017 21:01:29 +0000 [thread overview]
Message-ID: <bc5feee3-77d5-1850-cab0-eb37f128eaae@users.sourceforge.net> (raw)
In-Reply-To: <1494363154.20782.7.camel@perches.com>
> Perl is odd enough already adding more non-capture groups
> when the arguments are clearly specified is harder to read.
How do you think about to reformat the affected alternations?
Will it become appropriate to give each element a separate line there?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: checkpatch: Adjust regular expressions in $logFunctions
Date: Tue, 9 May 2017 23:01:29 +0200 [thread overview]
Message-ID: <bc5feee3-77d5-1850-cab0-eb37f128eaae@users.sourceforge.net> (raw)
In-Reply-To: <1494363154.20782.7.camel@perches.com>
> Perl is odd enough already adding more non-capture groups
> when the arguments are clearly specified is harder to read.
How do you think about to reformat the affected alternations?
Will it become appropriate to give each element a separate line there?
Regards,
Markus
next prev parent reply other threads:[~2017-05-09 21:01 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
2017-05-09 20:52 ` Joe Perches
2017-05-09 21:01 ` SF Markus Elfring [this message]
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=bc5feee3-77d5-1850-cab0-eb37f128eaae@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--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.