From: ebiederm@xmission.com (Eric W. Biederman)
To: Al Viro <viro@ZenIV.linux.org.uk>
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 11:49:53 -0800 [thread overview]
Message-ID: <87d2xuez32.fsf@xmission.com> (raw)
In-Reply-To: <20121228160927.GY4939@ZenIV.linux.org.uk> (Al Viro's message of "Fri, 28 Dec 2012 16:09:27 +0000")
Al Viro <viro@ZenIV.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.
Eric
next prev parent reply other threads:[~2012-12-28 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+8YGd6UqfbzEHOb2NUL5p3EF4OECVq7yc2vRV3GViVT64CTbQ@mail.gmail.com>
[not found] ` <20121227184034.GA2982@debian.debian>
[not found] ` <CABuSbKbk5DdhvuwYUeLkm=eub1CsSaOB_oX7bkBZcAV_MNsSdg@mail.gmail.com>
2012-12-28 4:49 ` anish singh
2012-12-28 5:12 ` amit mehta
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 ` how to look for source code in kernel Al Viro
2012-12-28 19:49 ` Eric W. Biederman [this message]
2012-12-28 20:42 ` Jonathan Neuschäfer
2012-12-28 21:31 ` Joe Perches
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=87d2xuez32.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=anish198519851985@gmail.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 \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome