From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: add TAGS target in testsuite
Date: Mon, 07 Mar 2011 18:43:00 -0000 [thread overview]
Message-ID: <83ipvuhko1.fsf@gnu.org> (raw)
In-Reply-To: <m3vczun9qt.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 07 Mar 2011 10:03:38 -0700
>
> I am undecided as to whether I should add this to gdb/TAGS via `etags
> --include'. If you use etags, and have an opinion, let me know.
IMO, it only makes sense to add this to gdb/TAGS if the additional
tags get into the GDB binary. The test suite does not satisfy this
requirement (unlike, say, portions of Emacs implemented in Lisp).
TAGS tables are used when you develop a package and need to quickly
find the implementation of certain functionalities of that package.
Anything that is not part of the package functionality should be on a
separate TAGS file.
next prev parent reply other threads:[~2011-03-07 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 17:24 Tom Tromey
2011-03-07 18:00 ` Pierre Muller
[not found] ` <21165.0532474325$1299518488@news.gmane.org>
2011-03-07 18:06 ` Tom Tromey
2011-03-07 18:42 ` Eli Zaretskii
2011-03-08 1:11 ` Tom Tromey
2011-03-07 18:43 ` Eli Zaretskii [this message]
2011-03-07 20:10 ` FYI: " Michael Snyder
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=83ipvuhko1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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