public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: [ack94598@yahoo.com: [postmaster@sources.redhat.com] please get rid of my email addreess from your publicly readable archive]
Date: Mon, 27 Jan 2003 13:12:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.51.0301271037390.59857@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030126052254.GC1122@redhat.com>

On Sun, 26 Jan 2003, Christopher Faylor wrote:
> However, my lack of sympathy aside, should we work on instituting some
> kind of "munge my email address" request?

I don't see why we should.  Now, if somebody wants to invest his/her time
and effort, that's certainly fine, but...

> I know I keep asking this question, and I really don't want to take any
> of my personal time to do something like this but the requests are on
> the rise.  Some people are even making legal threats to Red Hat over
> this issue.

...these legal threats are ridiculous (at least under those legal systems
I know).

Angela Marie Thomas wrote:
> You can reduce Red Hat liability by ensuring the initial "welcome
> to this list mail" let's them know the risks.

This won't suffice, as most of our lists are open (that is, not
subscriber-only).  What we for GCC is having

  Please send comments on these web pages and GCC to our public mailing
  list at gcc@gnu.org or gcc@gcc.gnu.org, [...]

in the footer of all web pages -- note "our public mailing lists".

Gerald
-- 
Gerald Pfeifer (Jerry)   gerald@pfeifer.com   http://www.pfeifer.com/gerald/

      parent reply	other threads:[~2003-01-27 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26  5:22 Christopher Faylor
2003-01-26  9:50 ` Angela Marie Thomas
2003-01-27 13:12 ` Gerald Pfeifer [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=Pine.BSF.4.51.0301271037390.59857@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=cgf@redhat.com \
    --cc=overseers@sources.redhat.com \
    /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).