From: Alex Belits <abelits@phobos.illtel.denver.co.us>
To: anish singh <anish198519851985@gmail.com>
Cc: "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: Thu, 27 Dec 2012 21:37:22 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212272137010.15278@mercury> (raw)
In-Reply-To: <CAK7N6vqw+DVSVaCXqiQBVa_d2o-rg-oA5t8+6WNaZ9Mb_iQqdw@mail.gmail.com>
On Fri, 28 Dec 2012, anish singh wrote:
>>> have source insight.We can use wine in linux but that sucks.
>> Funny you say that!
>> Never heard of cscope, ctags ?
> It is not as convenient as source insight or is it?
There is also LXR.
If it's not good enough for you, then don't look at it.
next prev parent reply other threads:[~2012-12-28 6:07 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 [this message]
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
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=alpine.DEB.2.02.1212272137010.15278@mercury \
--to=abelits@phobos.illtel.denver.co.us \
--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 \
/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
all inboxes | Powered by JetHome®