From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: help out make TAGS
Date: Fri, 09 Feb 2001 09:22:00 -0000 [thread overview]
Message-ID: <20010209122256.D18480@redhat.com> (raw)
In-Reply-To: <3A834A05.E7DBBC57@cygnus.com>
On Thu, Feb 08, 2001 at 05:38:13PM -0800, Andrew Cagney wrote:
>jkingdon@engr.sgi.com wrote:
>>
>> Seems like "make TAGS" has bitrotted a bit lately. OK to commit the
>> enclosed patch? I don't know whether it fixes everything, but it
>> works for me and is an improvement.
>>
>> Jim Kingdon
>> jkingdon@engr.sgi.com
>>
>> 2001-02-08 Jim Kingdon <jkingdon@engr.sgi.com>
>>
>> Updates to "make TAGS":
>> * Makefile.in (ALLDEPFILES): Remove altos-xdep.c arm-convert.s
>> arm-xdep.c convex-tdep.c convex-xdep.c pyr-tdep.c pyr-xdep.c
>> tahoe-tdep.c.
>> (TAGFILES_NO_SRCDIR): Add $(SUBDIR_CLI_SRCS).
>
>Yes, fine and thanks! Other people may want to keep an eye out for other
>bitrot caused by me removing several targets.
Doesn't Tom Tromey have a patch in the queue dealing with TAGS issues?
cgf
prev parent reply other threads:[~2001-02-09 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200102090129.UAA15637@panix2.panix.com>
2001-02-09 0:01 ` Eli Zaretskii
[not found] ` <3A834A05.E7DBBC57@cygnus.com>
2001-02-09 9:22 ` Christopher Faylor [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=20010209122256.D18480@redhat.com \
--to=cgf@redhat.com \
--cc=gdb-patches@sources.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