From: Brett Smith <brett@gnu.org>
To: gcc@gcc.gnu.org
Subject: [info@fsf.org: GCC bounds checking]
Date: Tue, 15 Oct 2002 14:02:00 -0000 [thread overview]
Message-ID: <20021015172130.GH1435@gnu.org> (raw)
Greetings,
This is a report about the GCC web page which was sent to <gnu@gnu.org>.
I'll leave it to you to decide what to do with it.
Thanks,
----- Forwarded message from RE <eagle888@bellsouth.net> -----
Subject: GCC bounds checking
From: RE <eagle888@bellsouth.net>
Date: Sun, 13 Oct 2002 07:59:34 -0400
Reply-To: info@fsf.org
X-Spam-Status: No, hits=-0.3 required=5.0
tests=IN_REP_TO,MISSING_HEADERS,SPAM_PHRASE_02_03
version=2.42
Hello!
Please either delete or fix the bounds checking link. It takes you to a page
of http://web.inter.nl.net/hcc/Haj.Ten.Brugge/
On this page there is not a valid email address and also none of the code
compiles!!! You get compiles errors on all versions!!
This is worthless!
----- End forwarded message -----
--
Brett Smith
Free Software Foundation | Phone: +1-617-542-5942
59 Temple Place, Suite 330 | Fax: +1-617-542-2652
Boston, MA 02111-1307 USA | Web: http://www.gnu.org
next reply other threads:[~2002-10-15 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 14:02 Brett Smith [this message]
2002-10-16 10:47 ` Janis Johnson
2002-10-17 7:21 ` RE
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=20021015172130.GH1435@gnu.org \
--to=brett@gnu.org \
--cc=gcc@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: link
Be 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).