From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Ian Lance Taylor <iant@google.com>, overseers@gcc.gnu.org
Subject: Re: [Michael Matz] Re: Don't let search bots look at buglist.cgi
Date: Tue, 17 May 2011 16:42:00 -0000 [thread overview]
Message-ID: <20110517164216.GA32319@ednor.casa.cgf.cx> (raw)
In-Reply-To: <mcript9z9mu.fsf@coign.corp.google.com>
On Tue, May 17, 2011 at 07:26:01AM -0700, Ian Lance Taylor wrote:
>Btw. FWIW, I had a quick look at one of the httpd log files, and in seven
>hours on last Saturday (from 5:30 to 12:30), there were overall 435203 GET
>requests, and 391319 of them came from our own MnoGoSearch engine, that's
>90%. Granted many are then in fact 304 (not modified) responses, but
>still, perhaps the eagerness of our own crawler can be turned down a bit.
Isn't MnoGoSearch doing what it's supposed to be doing? I don't see why we'd
turn it down.
prev parent reply other threads:[~2011-05-17 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 14:26 Ian Lance Taylor
2011-05-17 16:42 ` Christopher Faylor [this message]
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=20110517164216.GA32319@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=iant@google.com \
--cc=overseers@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).