public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug translation/21768] [3.4 regression] ICE in error message due to violation of coding conventions Date: Mon, 04 Jul 2005 09:53:00 -0000 [thread overview] Message-ID: <20050704095353.14725.qmail@sourceware.org> (raw) In-Reply-To: <20050526144535.21768.reichelt@gcc.gnu.org> ------- Additional Comments From reichelt at gcc dot gnu dot org 2005-07-04 09:53 ------- Changing component, since we are only missing the updated .po file. -- What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |translation http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21768
next prev parent reply other threads:[~2005-07-04 9:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-26 14:50 [Bug c++/21768] New: [3.4/4.0/4.1 " reichelt at gcc dot gnu dot org 2005-05-26 14:56 ` [Bug c++/21768] " reichelt at gcc dot gnu dot org 2005-05-26 15:47 ` pinskia at gcc dot gnu dot org 2005-05-26 16:10 ` cvs-commit at gcc dot gnu dot org 2005-05-26 16:14 ` cvs-commit at gcc dot gnu dot org 2005-05-26 16:17 ` cvs-commit at gcc dot gnu dot org 2005-05-26 16:41 ` reichelt at gcc dot gnu dot org 2005-05-26 16:56 ` reichelt at gcc dot gnu dot org 2005-06-29 14:02 ` [Bug c++/21768] [3.4 " reichelt at gcc dot gnu dot org 2005-07-04 9:53 ` reichelt at gcc dot gnu dot org [this message] 2005-08-31 13:47 ` [Bug translation/21768] " bonzini at gcc dot gnu dot org 2005-08-31 15:43 ` reichelt at igpm dot rwth-aachen dot de [not found] <bug-21768-1771@http.gcc.gnu.org/bugzilla/> 2005-10-07 4:04 ` gdr at gcc dot gnu dot org 2006-02-28 15:38 ` gdr at gcc dot gnu dot org
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=20050704095353.14725.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).