public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Gerald Pfeifer <gerald@pfeifer.com>, overseers@sourceware.org
Subject: Re: [Con Validas] URL block request from googlebot
Date: Sun, 11 Jan 2015 18:10:00 -0000	[thread overview]
Message-ID: <20150111181017.GA7659@ednor.casa.cgf.cx> (raw)
In-Reply-To: <alpine.LSU.2.11.1501110853590.17406@tuna.site>

On Sun, Jan 11, 2015 at 09:05:06AM +0100, Gerald Pfeifer wrote:
>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.

FYI, Frank has already turned down the request but the person is now
asking for an explanation.

I am against doing it because:

1) I think the request is stupid and I have a hard time making myself do
things that I think are stupid when I'm not being paid to do so.

2) The slippery slope - if we do this for him then we have no reason not
to do it for everyone.  And, if we do this one thing then, IMO, it opens
up the door for more arguing about modifying mailing list posts.  They
aren't the same thing but I wouldn't want to have to spend any time at
all arguing that point.

cgf

      reply	other threads:[~2015-01-11 18:10 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
2015-01-11 18:10   ` Christopher Faylor [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=20150111181017.GA7659@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=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).