public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org,
nobody@gcc.gnu.org, tromey@gcc.gnu.org, uweigand@de.ibm.com
Subject: Re: libgcj/8142: '$' in class names vs. dlopen 'dynamic string tokens'
Date: Sat, 02 Nov 2002 15:35:00 -0000 [thread overview]
Message-ID: <20021102233501.15315.qmail@sources.redhat.com> (raw)
Synopsis: '$' in class names vs. dlopen 'dynamic string tokens'
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Sat Nov 2 15:35:01 2002
Responsible-Changed-Why:
I'm handling the administrivia
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Sat Nov 2 15:35:01 2002
State-Changed-Why:
A patch to fix this was checked in
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8142
next reply other threads:[~2002-11-02 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 15:35 tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 6:36 uweigand
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=20021102233501.15315.qmail@sources.redhat.com \
--to=tromey@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=java-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=uweigand@de.ibm.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).