[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121228204252.GA3005@debian.debian>
Date: Fri, 28 Dec 2012 21:42:53 +0100
From: Jonathan Neuschäfer <j.neuschaefer@....net>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Al Viro <viro@...IV.linux.org.uk>,
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, Dec 28, 2012 at 11:49:53AM -0800, Eric W. Biederman wrote:
> Al Viro <viro@...IV.linux.org.uk> writes:
>
> > 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?
>
> I haven't learned it yet. git-ls-files is a lot better than find
> speed wise so is very much worth doing. I haven't a clue if
> there is an advantage to git-grep, over just knowing find, xargs, and
> grep.
Brevity.
Jonathan
--
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