public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: jakub@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/8022: gcc 3.2 Solaris 64 bit shared libraries Date: Mon, 03 Feb 2003 17:16:00 -0000 [thread overview] Message-ID: <20030203171600.10376.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8022; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: "David S. Miller" <davem@redhat.com> Cc: gcc-bugs@gcc.gnu.org, <hyc@symas.com>, <gcc-gnats@gcc.gnu.org> Subject: Re: target/8022: gcc 3.2 Solaris 64 bit shared libraries Date: Mon, 3 Feb 2003 11:10:45 -0600 (CST) On Sun, 2 Feb 2003, David S. Miller wrote: > I would like to ask that this gets assigned to one of the other > sparc maintainers as I currently lack any time to look into > GNATS reports or any GCC issues at all. Done -- I took the next one in the list from the Maintainers file. I'm just trying to get someone into the field to at least look at the patch that's given in the report. If nobody does, the report stays open forever. Thanks for at least this kind of feedback :-) W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-02-03 17:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-03 17:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-03 18:36 Howard Chu 2003-02-03 17:08 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=20030203171600.10376.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --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).