public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org To: catherin@ca.ibm.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lerdsuwa@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/8806: gcc accepts bad argument for template template parameter Date: Thu, 19 Dec 2002 07:04:00 -0000 [thread overview] Message-ID: <20021219150436.7818.qmail@sources.redhat.com> (raw) Synopsis: gcc accepts bad argument for template template parameter Responsible-Changed-From-To: unassigned->lerdsuwa Responsible-Changed-By: lerdsuwa Responsible-Changed-When: Thu Dec 19 07:04:36 2002 Responsible-Changed-Why: I will fix this in the trunk after new parser merge. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8806
next reply other threads:[~2002-12-19 15:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-19 7:04 lerdsuwa [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-04 6:46 Wolfgang Bangerth 2002-12-04 6:31 reichelt 2002-12-04 6:18 catherin
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=20021219150436.7818.qmail@sources.redhat.com \ --to=lerdsuwa@gcc.gnu.org \ --cc=catherin@ca.ibm.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).