public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@sourceware.org
Subject: Re: [Con Validas] URL block request from googlebot
Date: Sun, 11 Jan 2015 08:05:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1501110853590.17406@tuna.site> (raw)
In-Reply-To: <m3sig9k3ub.fsf@pepe.airs.com>

On Saturday 2014-12-20 20:46, Ian Lance Taylor wrote:
> I haven't seen this kind of request before.  Any opinions?

I've looked at this thrice over the course of a two weeks, and
still am struggling.

Since this is not about removing contents, just taking it off
the search engine map with robots.txt, it's less problematic
(and we would not "censor").  On the other hand, this posting
really seems harmless enough and I don't understand.  On the
third hand, such an approach sipmly does not scale.

So, I'd not to it personally, though I would not complain bitterly 
if someone else did.

Gerald

  reply	other threads:[~2015-01-11  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 20:26 Ian Lance Taylor
2015-01-11  8:05 ` Gerald Pfeifer [this message]
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=alpine.LSU.2.11.1501110853590.17406@tuna.site \
    --to=gerald@pfeifer.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).