From: Mark Kettenis <kettenis@wins.uva.nl>
To: kevinb@cygnus.com
Cc: ac131313@cygnus.com, kevinb@cygnus.com, gdb@sources.redhat.com
Subject: Re: [RFC] ptid_get_pid function vs. PIDGET macro
Date: Wed, 10 Oct 2001 14:02:00 -0000 [thread overview]
Message-ID: <200110102102.f9AL26o00251@delius.kettenis.local> (raw)
In-Reply-To: <1011010070055.ZM12213@ocotillo.lan>
Date: Wed, 10 Oct 2001 00:00:55 -0700
From: Kevin Buettner <kevinb@cygnus.com>
Mark, did you want to do this? Or should I whip up a perl script?
I intended to do things by hand, gradually converting the source files
whenever I felt like it. I did change thread-db.c some time ago and
since I wanted to make some further changes to it, I wondered whether
I should throw away these changes or not. I'll commit the changes
somewehere in the near future.
Mark
prev parent reply other threads:[~2001-10-10 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 5:58 Mark Kettenis
2001-10-08 15:54 ` Kevin Buettner
2001-10-09 22:28 ` Andrew Cagney
2001-10-10 0:01 ` Kevin Buettner
2001-10-10 14:02 ` Mark Kettenis [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=200110102102.f9AL26o00251@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=ac131313@cygnus.com \
--cc=gdb@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