From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: getting rid of the target stack
Date: Thu, 27 Jun 2002 06:23:00 -0000 [thread overview]
Message-ID: <np8z503lek.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <20020627052529.GA15598@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> I really like this proposal. Where particularly were you thinking of
> starting?
No particular time. This isn't even something that's related to any
internal Red Hat plan, unlike the thread-local storage, namespace
stuff, etc. It just occurred to me how it could be done
incrementally.
> (and, hey, whatever happened to the namespace work we were discussing
> earlier?)
It's on my schedule somewhere after thread-local storage and Dwarf 2
duplicate removal. I don't remember the dates too well, but I think
that means I'll be able to start pitching in in Sept/Oct.
next prev parent reply other threads:[~2002-06-27 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 22:13 Jim Blandy
2002-06-26 22:25 ` Daniel Jacobowitz
2002-06-27 6:23 ` Jim Blandy [this message]
2002-07-01 9:38 ` Namespaces; Was: " Andrew Cagney
2002-06-27 7:44 ` Andrew Cagney
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=np8z503lek.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).