From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: anish singh <anish198519851985@gmail.com>,
amit mehta <gmate.amit@gmail.com>,
Henrique Rodrigues <henriquesilvar@gmail.com>,
kishore kumar <kishoreopen@gmail.com>,
Jonathan Neusch??fer <j.neuschaefer@gmx.net>,
linux-kernel@vger.kernel.org, Kernelnewbies@kernelnewbies.org
Subject: Re: how to look for source code in kernel
Date: Fri, 28 Dec 2012 16:09:27 +0000 [thread overview]
Message-ID: <20121228160927.GY4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87a9syhbma.fsf@xmission.com>
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?
next prev parent reply other threads:[~2012-12-28 16:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 17:31 how to look for source code in kernel kishore kumar
2012-12-27 18:40 ` Jonathan Neuschäfer
2012-12-27 19:53 ` Henrique Rodrigues
2012-12-28 4:49 ` anish singh
2012-12-28 4:49 ` anish singh
2012-12-28 5:12 ` amit mehta
2012-12-28 5:12 ` amit mehta
2012-12-28 5:19 ` anish singh
2012-12-28 5:19 ` anish singh
2012-12-28 5:37 ` Alex Belits
2012-12-28 7:36 ` Eric W. Biederman
2012-12-28 13:07 ` Borislav Petkov
2012-12-28 22:03 ` Geert Uytterhoeven
2012-12-29 11:09 ` Borislav Petkov
2012-12-28 22:23 ` Guennadi Liakhovetski
2012-12-28 22:38 ` Jesper Juhl
2012-12-28 23:08 ` [PATCH] scripts/tags.sh: Fix regex syntax for etags Andreas Schwab
2012-12-28 23:22 ` Jesper Juhl
2013-01-13 21:23 ` Michal Marek
2012-12-28 16:09 ` Al Viro [this message]
2012-12-28 19:49 ` how to look for source code in kernel Eric W. Biederman
2012-12-28 20:42 ` Jonathan Neuschäfer
2012-12-28 20:42 ` Jonathan Neuschäfer
2012-12-28 21:31 ` Joe Perches
2012-12-28 9:49 ` Mulyadi Santosa
2012-12-28 10:11 ` Arun KS
2012-12-28 5:40 ` Chen Gang F T
2012-12-28 5:49 ` Chen Gang F T
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=20121228160927.GY4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=anish198519851985@gmail.com \
--cc=ebiederm@xmission.com \
--cc=gmate.amit@gmail.com \
--cc=henriquesilvar@gmail.com \
--cc=j.neuschaefer@gmx.net \
--cc=kishoreopen@gmail.com \
--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.