From: Richard Guenther <richard.guenther@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: overseers@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Don't let search bots look at buglist.cgi
Date: Mon, 16 May 2011 12:59:00 -0000 [thread overview]
Message-ID: <BANLkTim22-m_jqhHCiNiGKVs5km96t6M3w@mail.gmail.com> (raw)
In-Reply-To: <mcry62a7cau.fsf@coign.corp.google.com>
On Fri, May 13, 2011 at 7:14 PM, Ian Lance Taylor <iant@google.com> wrote:
> I noticed that buglist.cgi was taking quite a bit of CPU time. I looked
> at some of the long running instances, and they were coming from
> searchbots. I can't think of a good reason for this, so I have
> committed this patch to the gcc.gnu.org robots.txt file to not let
> searchbots search through lists of bugs. I plan to make a similar
> change on the sourceware.org and cygwin.com sides. Please let me know
> if this seems like a mistake.
>
> Does anybody have any experience with
> http://code.google.com/p/bugzilla-sitemap/ ? That might be a slightly
> better approach.
Shouldn't we keep searchbots way from bugzilla completely? Searchbots
can crawl the gcc-bugs mailinglist archives.
Richard.
> Ian
>
>
next prev parent reply other threads:[~2011-05-16 9:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 19:19 Ian Lance Taylor
2011-05-16 12:59 ` Richard Guenther [this message]
2011-05-16 13:17 ` Andrew Haley
2011-05-16 13:18 ` Michael Matz
2011-05-16 13:28 ` Andrew Haley
2011-05-16 13:32 ` Andreas Schwab
2011-05-16 13:34 ` Richard Guenther
2011-05-16 13:39 ` Andrew Haley
2011-05-16 13:42 ` Michael Matz
2011-05-16 13:42 ` Andrew Haley
2011-05-16 13:45 ` Michael Matz
2011-05-16 14:18 ` Andrew Haley
2011-05-16 14:37 ` Richard Guenther
2011-05-16 15:28 ` Andrew Haley
2011-05-17 7:17 ` Ian Lance Taylor
2011-05-17 11:12 ` Axel Freyn
2011-05-17 13:39 ` Michael Matz
2011-05-16 23:13 ` Ian Lance Taylor
2011-05-17 2:53 ` Joseph S. Myers
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=BANLkTim22-m_jqhHCiNiGKVs5km96t6M3w@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.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).