public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/9071] Warning for blocks not closed in same file as opened in Date: Mon, 19 Jan 2004 21:08:00 -0000 [thread overview] Message-ID: <20040119210810.23640.qmail@sources.redhat.com> (raw) In-Reply-To: <20021227153601.9071.debian-gcc@lists.debian.org> ------- Additional Comments From dberlin at gcc dot gnu dot org 2004-01-19 21:08 ------- They are auto-replies from debian's bug system. I changed the bug reporter so it would stop the mail loop. I wish the debian guys would stop putting auto-responders as the owners of bugs. There are quite a few. If you need to modify a bug that it cc'ed to a @bugs.debian.org address, please let me know first so i can change who owns it without it sending out email. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9071
next prev parent reply other threads:[~2004-01-19 21:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021227153601.9071.debian-gcc@lists.debian.org> 2004-01-19 21:05 ` dhazeghi at yahoo dot com 2004-01-19 21:08 ` dberlin at gcc dot gnu dot org [this message] 2004-01-19 21:10 ` owner at bugs dot debian dot org 2004-02-04 10:26 ` [Bug c/9071] " neil at gcc dot gnu dot org [not found] <20021227153601.9071.122103@bugs.debian.org> 2004-01-19 19:51 ` [Bug preprocessor/9071] " owner at bugs dot debian dot org 2004-01-19 20:08 ` owner at bugs dot debian dot org 2004-01-19 20:21 ` owner at bugs dot debian dot org 2004-01-19 20:39 ` owner at bugs dot debian dot org 2004-01-19 20:51 ` owner at bugs dot debian 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=20040119210810.23640.qmail@sources.redhat.com \ --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).