From mboxrd@z Thu Jan 1 00:00:00 1970 From: j.neuschaefer@gmx.net (Jonathan =?utf-8?Q?Neusch=C3=A4fer?=) Date: Fri, 28 Dec 2012 21:42:53 +0100 Subject: how to look for source code in kernel In-Reply-To: <87d2xuez32.fsf@xmission.com> References: <20121227184034.GA2982@debian.debian> <87a9syhbma.fsf@xmission.com> <20121228160927.GY4939@ZenIV.linux.org.uk> <87d2xuez32.fsf@xmission.com> Message-ID: <20121228204252.GA3005@debian.debian> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Fri, Dec 28, 2012 at 11:49:53AM -0800, Eric W. Biederman wrote: > Al Viro 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