[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1356730299.31130.27.camel@joe-AO722>
Date: Fri, 28 Dec 2012 13:31:39 -0800
From: Joe Perches <joe@...ches.com>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
anish singh <anish198519851985@...il.com>,
amit mehta <gmate.amit@...il.com>,
Henrique Rodrigues <henriquesilvar@...il.com>,
kishore kumar <kishoreopen@...il.com>,
Jonathan Neusch??fer <j.neuschaefer@....net>,
linux-kernel@...r.kernel.org, Kernelnewbies@...nelnewbies.org
Subject: Re: how to look for source code in kernel
On Fri, 2012-12-28 at 16:09 +0000, Al Viro wrote:
> On Thu, Dec 27, 2012 at 11:36:13PM -0800, Eric W. Biederman wrote:
> > But then I am probably peculiar keeping an index of the source code in
> > my head. When I need to look for something and I don't know where to
> > find it I do.
> >
> > git-ls-files | xargs fgrep 'struct f2fs_inode'
>
> What's wrong with git grep?
Positive: it loads multiple cpus with very little file I/O
Negative: it doesn't use -P very well.
it won't spans lines like:
struct name
{
with git grep -P "\bstruct\s+\w+\s*{"
(the last grep that does I believe is 2.54)
--
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