From: Jason Molenda <jason-swarelist@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sources.redhat.com
Subject: Re: gcc maintainer available?
Date: Fri, 06 Aug 2004 09:59:00 -0000 [thread overview]
Message-ID: <20040806013549.A5960@molenda.com> (raw)
In-Reply-To: <Pine.BSF.4.61.0408061000100.55773@acrux.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Fri, Aug 06, 2004 at 10:04:50AM +0200
On Fri, Aug 06, 2004 at 10:04:50AM +0200, Gerald Pfeifer wrote:
> On Tue, 20 Jul 2004, Jason Molenda wrote:
> > How about, "All of our e-mail archives are scanned by spam e-mail
> > harvester bots; post and be harvested. You've been warned."
>
> You are a bit extreme, aren't you. ;-)
I was only half joking when I wrote that. Our goal is to tell
people that when they post an e-mail to the list, their e-mail
address is going to be harvested. So why not just say that? It
doesn't have to be as mean-spirited as my suggestion, but saying
"it is archived publicly" and hoping that the reader understands
everything this entails leaves it open for more hurt feelings and
whiny e-mails asking for archive changes.
I have no sway over what goes on the gcc.gnu.org site of course,
I'm just a disinterested third party. But I say we cut the BS and
say what we mean: You post, it's archived, and the e-mail addresses
will all be harvested. Welcome to life in the big net.
J
prev parent reply other threads:[~2004-08-06 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 19:48 gcc maintainer available? [dkegel: [postmaster] Mistaken post removal request] Christopher Faylor
2004-07-20 20:55 ` Gerald Pfeifer
2004-07-20 21:26 ` Christopher Faylor
2004-07-20 21:29 ` Jason Molenda
2004-07-20 21:43 ` Matthew Galgoci
2004-07-21 0:18 ` Christopher Faylor
2004-08-06 8:35 ` gcc maintainer available? Gerald Pfeifer
2004-08-06 9:59 ` Jason Molenda [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=20040806013549.A5960@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sources.redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).