From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org, Aldy Hernandez <aldyh@redhat.com>
Cc: Paolo Carlini <pcarlini@unitus.it>, gcc@gcc.gnu.org
Subject: Re: bug in search engine
Date: Thu, 09 Oct 2003 15:37:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0310091730320.90326@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <3F857E11.9080401@unitus.it>
On Thu, 9 Oct 2003, Paolo Carlini wrote:
>> Try to search for... "foo --bar" on either the GCC or the GCC patches
>> search engine.
> Funny!
It looks funny, but it might well be exploitable (so it would have been
better not to post this to the widely spread gcc list).
I have thus completely disabled the whole search engine for now¹ until
H-P or someone else has had a closer look.
Gerald
¹ chmod a-x htsearch
next prev parent reply other threads:[~2003-10-09 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 15:25 Aldy Hernandez
2003-10-09 15:32 ` Paolo Carlini
2003-10-09 15:37 ` Gerald Pfeifer [this message]
2003-10-09 15:47 ` Aldy Hernandez
2003-10-09 16:05 Lee Manickum
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=Pine.BSF.4.58.0310091730320.90326@naos.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=pcarlini@unitus.it \
/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).