From: Mark Kettenis <kettenis@gnu.org>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com, msnyder@redhat.com
Subject: Re: [rfa] Rename thread-db.c to linux-thread-db.c.
Date: Wed, 10 Nov 2004 18:11:00 -0000 [thread overview]
Message-ID: <200411101810.iAAIA98s094958@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20041109032415.GA4083@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 8 Nov 2004 22:24:15 -0500)
Date: Mon, 8 Nov 2004 22:24:15 -0500
From: Daniel Jacobowitz <drow@false.org>
Mark asked me to rename thread-db.c, to make it clear that it is a GNU/Linux
specific file, before I made further structural changes to it. This patch
renames it to linux-thread-db.c.
No djgpp tweaks are necessary (it doesn't conflict with anything; we used to
have a linux-thread.c, IIRC, but it's long dead).
OK to commit? I've omitted the actual rename from the patch.
If you don't hear from Michael soon, go ahead!
Mark
next prev parent reply other threads:[~2004-11-10 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 3:24 Daniel Jacobowitz
2004-11-10 18:11 ` Mark Kettenis [this message]
2004-11-12 20:26 ` Michael Snyder
2004-11-14 18:49 ` Daniel Jacobowitz
2004-11-14 18:53 ` Daniel Jacobowitz
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=200411101810.iAAIA98s094958@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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