From: Jim Blandy <jimb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: initial TLS patch
Date: Wed, 03 Jul 2002 13:10:00 -0000 [thread overview]
Message-ID: <npadp8bo7e.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3D223796.A3911C80@redhat.com>
Michael Snyder <msnyder@redhat.com> writes:
> As a preliminary comment, I think the design is pretty sound.
> I haven't finished my "eyeball review", but I hope to look at
> it some more tomorrow (before the 4th of july break).
Okay, great.
> One thing -- I'm a little leary about the target module
> actually building a struct value. Seems like that should
> be done at a higher level.
Yes, I agree that's somewhat questionable. I'm going to take that out
for this pass; when thread_db provides the support we need to do
fancier things, we can revisit the question.
next prev parent reply other threads:[~2002-07-03 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 8:23 Jim Blandy
2002-07-02 10:08 ` Daniel Berlin
2002-07-03 2:39 ` Michael Snyder
2002-07-03 13:10 ` Jim Blandy [this message]
2002-07-03 8:28 ` Andrew Cagney
2002-07-03 11:30 ` Jim Blandy
2002-07-08 19:19 ` Andrew Cagney
2002-07-08 20:48 ` Jim Blandy
2002-07-08 20:06 ` Andrew Cagney
2002-07-08 20:15 ` Jim Blandy
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=npadp8bo7e.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--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