public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: jsm28@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7748: Static objects in dynamic library with non-default priority not initialized
Date: Fri, 20 Dec 2002 03:36:00 -0000 [thread overview]
Message-ID: <20021220113604.27148.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7748; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <bangerth@dealii.org>, <gcc-bugs@gcc.gnu.org>, <jrheath@ca.ibm.com>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: c++/7748: Static objects in dynamic library with non-default
priority not initialized
Date: Fri, 20 Dec 2002 11:30:49 +0000 (GMT)
On 20 Dec 2002 bangerth@dealii.org wrote:
> Synopsis: Static objects in dynamic library with non-default priority not initialized
>
> Responsible-Changed-From-To: unassigned->jsm28
> Responsible-Changed-By: bangerth
> Responsible-Changed-When: Thu Dec 19 18:09:06 2002
> Responsible-Changed-Why:
> The last to change the respective code. If you feel you
> are not the right person to ask, I'll be happy to undo
> this.
I don't even know what code you're talking about. If cvs annotate has
indicated the last change to it was some global change such as spelling
fixes or table-driven attributes, you need to find someone who has
actually worked on that code locally.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2002-12-20 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 3:36 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 9:06 bangerth
2002-12-20 9:06 Wolfgang Bangerth
2002-12-19 18:09 bangerth
2002-12-13 14:06 jrheath
2002-08-28 12:06 jrheath
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=20021220113604.27148.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=jsm28@gcc.gnu.org \
/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).