kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: j.neuschaefer@gmx.net (Jonathan Neuschäfer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to look for source code in kernel
Date: Fri, 28 Dec 2012 21:42:53 +0100	[thread overview]
Message-ID: <20121228204252.GA3005@debian.debian> (raw)
In-Reply-To: <87d2xuez32.fsf@xmission.com>

On Fri, Dec 28, 2012 at 11:49:53AM -0800, Eric W. Biederman wrote:
> 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.

Brevity.

Jonathan

      parent reply	other threads:[~2012-12-28 20:42 UTC|newest]

Thread overview: 9+ 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  5:12       ` amit mehta
2012-12-28  5:19         ` anish singh
2012-12-28  9:49           ` Mulyadi Santosa
2012-12-28 10:11             ` Arun KS
     [not found]           ` <87a9syhbma.fsf@xmission.com>
     [not found]             ` <20121228160927.GY4939@ZenIV.linux.org.uk>
     [not found]               ` <87d2xuez32.fsf@xmission.com>
2012-12-28 20:42                 ` Jonathan Neuschäfer [this message]

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=20121228204252.GA3005@debian.debian \
    --to=j.neuschaefer@gmx.net \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).