public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: davem@gcc.gnu.org, davem@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hyc@symas.com, jakub@gcc.gnu.org Subject: Re: target/8022: gcc 3.2 Solaris 64 bit shared libraries Date: Mon, 03 Feb 2003 17:08:00 -0000 [thread overview] Message-ID: <20030203170836.2189.qmail@sources.redhat.com> (raw) Synopsis: gcc 3.2 Solaris 64 bit shared libraries Responsible-Changed-From-To: davem->jakub Responsible-Changed-By: bangerth Responsible-Changed-When: Mon Feb 3 17:08:36 2003 Responsible-Changed-Why: DaveM wants to be replaced as the one responsible for this one. Let's try the next one in the list of SPARC maintainers... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8022
next reply other threads:[~2003-02-03 17:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-03 17:08 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-03 18:36 Howard Chu 2003-02-03 17:16 Wolfgang Bangerth 2003-02-03 4:26 David S. Miller 2003-02-02 23:17 bangerth
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=20030203170836.2189.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=davem@gcc.gnu.org \ --cc=davem@redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hyc@symas.com \ --cc=jakub@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: linkBe 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).