From: Ian Lance Taylor <ian@airs.com>
To: overseers@sourceware.org
Subject: [Con Validas] URL block request from googlebot
Date: Sun, 21 Dec 2014 20:26:00 -0000 [thread overview]
Message-ID: <m3sig9k3ub.fsf@pepe.airs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
I haven't seen this kind of request before. Any opinions?
Ian
[-- Attachment #2: Type: message/rfc822, Size: 3179 bytes --]
From: Con Validas <cvalidas@optusnet.com.au>
To: sourcemaster@sourceware.org, ian@airs.com
Subject: URL block request from googlebot
Date: Sun, 21 Dec 2014 10:30:41 +1100
Message-ID: <549606A1.7060206@optusnet.com.au>
Dear Webmaster,
I would like to request a Google Search URL block for one of your html
pages on the sourceware.org docbook-apps mailing list. The page in
question is
http://www.sourceware.org/ml/docbook-apps/2002-q4/msg00219.html.
This page returns as a result of a Google search on my name and I
would rather it be disallowed from indexing by Google robots. The post
is perfectly fine within the mailing list and I am not requesting a
removal of the post. A 12+ year old post associated with my name
however is something I would rather be viewed by the docbook community
as opposed to a google audience. It is a personal preference but one I
hope you can understand.
I believe this can be resolved by a simple entry in robots.txt or a
meta tag in the html file.
I sincerely appreciate you taking the time to read my request and I
hope you can accommodate it. I look forward to hearing back from you.
Kind Regards,
Con Validas
next reply other threads:[~2014-12-21 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 20:26 Ian Lance Taylor [this message]
2015-01-11 8:05 ` Gerald Pfeifer
2015-01-11 18:10 ` Christopher Faylor
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=m3sig9k3ub.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=overseers@sourceware.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).