[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1253825489.18939.180.camel@laptop>
Date: Thu, 24 Sep 2009 22:51:29 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
Tom Zanussi <tzanussi@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Li Zefan <lizf@...fujitsu.com>
Subject: Re: [GIT PULL v2] bkl tracepoints + filter regex support
On Thu, 2009-09-24 at 22:44 +0200, Frederic Weisbecker wrote:
> I don't quite understand why.
>
> Typing file == "*reiserfs*" looks more intuitive.
>
> It's true that the filters should stay tight to the C syntax,
> but following this guideline up to the point that we are forced to
> use function expressions to do something that can be expressed
> much more easily and more intuitively (IMHO), that all sounds like
> an overkill.
>
> The use of glob is a very primary need for filters, it's
> so much a basic requirement for it that it should be native
> in its language.
The thing that my fingers know is awk syntax:
file ~ /reiserfs/
I'd very much prefer to keep == for strict equality, however the above
requires actual regex bits.
Remember, there are no second chances for the filter syntax anymore.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists