public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Mark Wielaard <mark@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 509d9104a9ae8246122c3d97b3e33ddf30416f93 Date: Fri, 1 Mar 2024 13:38:09 +0000 (GMT) [thread overview] Message-ID: <20240301133809.1BC953858408@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 509d9104a9ae8246122c3d97b3e33ddf30416f93 (commit) from 57e980697644832bf9e35a3722ae286ebdca3587 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 509d9104a9ae8246122c3d97b3e33ddf30416f93 Author: Mark Wielaard <mark@klomp.org> Date: Fri Mar 1 14:33:39 2024 +0100 robots.txt: Disallow various wiki actions It is fine for robots to crawl the wiki pages, but they should perform actions, generate huge diffs, search/highlight pages or generate calendars. diff --git a/htdocs/robots.txt b/htdocs/robots.txt index 057c5899..36be4d13 100644 --- a/htdocs/robots.txt +++ b/htdocs/robots.txt @@ -14,4 +14,8 @@ Disallow: /bugzilla/show_bug.cgi*ctype=xml* Disallow: /bugzilla/attachment.cgi Disallow: /bugzilla/showdependencygraph.cgi Disallow: /bugzilla/showdependencytree.cgi +Disallow: /wiki/*?action=* +Disallow: /wiki/*?diffs=* +Disallow: /wiki/*?highlight=* +Disallow: /wiki/*?calparms=* Crawl-Delay: 60 ----------------------------------------------------------------------- Summary of changes: htdocs/robots.txt | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-03-01 13:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240301133809.1BC953858408@sourceware.org \ --to=mark@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).