From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] solib-svr4 cleanups
Date: Tue, 06 Mar 2001 15:01:00 -0000 [thread overview]
Message-ID: <3AA4E937.50C25898@cygnus.com> (raw)
In-Reply-To: <1010306002007.ZM8108@ocotillo.lan>
> BTW, I would be more inclined to use solib-lm-tbd.c or perhaps
> solib-lm-legacy.c. (The only problem that I have with "tbd" is that
> it often means "to be determined" - or at least that's what I first
> thought of when I saw it.) Anyway, one of these names would cause this
> file to remain grouped with the other solib-* files. The use of
> either "tbd" or "legacy" in the name still enables all of the legacy
> file to be found via ``ls *tbd*''.
Doesn't worry me. Even solib-legacy.c
Andrew
next prev parent reply other threads:[~2001-03-06 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 12:01 Kevin Buettner
2001-03-05 8:11 ` Andrew Cagney
[not found] ` <ac131313@cygnus.com>
2001-03-05 16:20 ` Kevin Buettner
2001-03-05 17:16 ` Kevin Buettner
2001-03-06 0:48 ` Eli Zaretskii
2001-03-06 15:01 ` Andrew Cagney [this message]
2001-03-09 22:31 ` Kevin Buettner
2001-03-12 11:46 ` Michael Snyder
2001-03-12 11:55 ` Kevin Buettner
2001-03-12 15:40 ` 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=3AA4E937.50C25898@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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