On Fri, 07 Jun 2019 16:19:15 -0700, Bakul Shah said:
You can directly use search as follows:
-search 'Subject[ \t]:[ \t]*\[PATCH \.[0-9]'
[~] grep ^Subject Mail/linux-kernel/321805
Subject: Re: [PATCH 4.9 04/20] net: Fix for_each_netdev_feature on Big endian
[~] scan `pick +linux-kernel 321805 -search 'Subject: \[PATCH \.[0-9]' -and
-from email@example.com -list`
321805 * Thu 21Feb 7k Greg Kroah-Hartma Re: [PATCH 4.9 04/20] net:
Fix for_each_netdev_feature on Big endian <<On Thu, Feb 21,
[~] scan `pick +linux-kernel 321805 -search 'Subject: \[WOMBAT \.[0-9]'
-and -from firstname.lastname@example.org -list`
pick: no messages match specification
scan: no messages match specification
There's still something busticated here. Why did it match even with the Re: in
A modified grep(1) is used to perform the matching, so the full
(see ed(1)) facility is available within pattern. With -search,
pattern is used
directly, and with the others, the grep pattern constructed is:
I understand why that .* was causing me indigestion. But I'm having a hard
time matching "pattern is used directly" with what I'm seeing, unless -search
is *also* doing a split into component and pattern and constructing a grep
expression from the two that includes the .* implicitly?
Also, saw this under 'BUG' in the pick manpage:
The pattern syntax '[l-r]' is not supported; each letter to be matched must be
included within the square brackets.
However, '.[0-9]' matches 4.14 and 5.1 quite nicely.
Description: PGP signature