From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
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 21:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105162118230.30957@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mcraaem4c5n.fsf@coign.corp.google.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1267 bytes --]
On Mon, 16 May 2011, Ian Lance Taylor wrote:
> Richard Guenther <richard.guenther@gmail.com> writes:
>
> > 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.
>
> I don't see anything wrong with crawling bugzilla, though, and the
> resulting links should be better.
Indeed. I think the individual bugs, and the GCC-specific help texts
(such as describekeywords.cgi and describecomponents.cgi), should be
indexed.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2011-05-16 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 17:14 Ian Lance Taylor
2011-05-16 9:45 ` Richard Guenther
2011-05-16 20:35 ` Ian Lance Taylor
2011-05-16 21:20 ` Joseph S. Myers [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=Pine.LNX.4.64.1105162118230.30957@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=overseers@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).