From: Greg KH <gregkh@linuxfoundation.org>
To: xujialu <xujialu@vimux.org>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org,
masahiroy@kernel.org, akpm@linux-foundation.org,
mchehab+huawei@kernel.org
Subject: Re: [PATCH] scripts: gtags_files_generator.sh
Date: Sat, 25 Apr 2020 10:03:43 +0200 [thread overview]
Message-ID: <20200425080343.GA2048673@kroah.com> (raw)
In-Reply-To: <20200425073105.27796-1-xujialu@vimux.org>
On Sat, Apr 25, 2020 at 03:31:06PM +0800, xujialu wrote:
> Add a script to generate a gtags.files file.
>
> For navigating linux sources, it will be more efficient if gtags/cscope just
> collects source files that needed by compilation. The kernel makefiles already
> create *.cmd files that contain the files we needed, then just extracts files
> list from them and into gtags.files cause it's the default name list file for
> gtags.
>
> make defconfig
> make
> scripts/gtags_files_generator.sh
> gtags [-f gtags.files]
>
> Enjoy with vim+gtags. :)
What's wrong with just 'make gtags' that we currently have in the kernel
tree? Shouldn't that be sufficient, and if not, then you need to
explain why it isn't in your changelog.
thanks,
greg k-h
next prev parent reply other threads:[~2020-04-25 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200423095331.8032-1-xujialu@vimux.org>
2020-04-23 10:38 ` [PATCH] scripts: gtags_files_generator.sh Greg KH
[not found] ` <20200423143642.11788-1-xujialu@vimux.org>
[not found] ` <20200423143642.11788-2-xujialu@vimux.org>
2020-04-23 14:42 ` Greg KH
2020-04-23 14:44 ` Jonathan Corbet
[not found] ` <20200425073105.27796-1-xujialu@vimux.org>
2020-04-25 8:03 ` Greg KH [this message]
[not found] ` <20200426024436.7534-1-xujialu@vimux.org>
2020-04-26 7:09 ` Greg KH
2020-04-26 7:46 ` xujialu
2020-04-26 8:36 ` gregkh
[not found] ` <20200428053509.19564-1-xujialu@vimux.org>
2020-04-28 7:04 ` Greg KH
[not found] ` <20200428053509.19564-2-xujialu@vimux.org>
2020-04-28 7:06 ` [PATCH v2] scripts: scripts/tags.sh Greg KH
[not found] ` <20200502052619.26457-1-xujialu@vimux.org>
[not found] ` <20200502052619.26457-2-xujialu@vimux.org>
2020-05-12 2:51 ` [PATCH v4 1/2] scripts: Support compiled source, improved precise Masahiro Yamada
[not found] ` <20200514170945.24964-1-xujialu@vimux.org>
2020-05-21 6:29 ` Masahiro Yamada
[not found] ` <20200502052619.26457-3-xujialu@vimux.org>
2020-05-12 3:08 ` [PATCH v4 2/2] scripts: Add a intermediate file for 'make gtags' Masahiro Yamada
2020-04-28 7:52 ` [PATCH] scripts: gtags_files_generator.sh Masahiro Yamada
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=20200425080343.GA2048673@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=xujialu@vimux.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