From: Gerald Pfeifer <gerald@pfeifer.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: Confidentiality notices
Date: Mon, 01 Mar 2004 22:21:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0403012319030.67370@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.BSF.4.58.0401281915500.39845@acrux.dbai.tuwien.ac.at>
On Wed, 28 Jan 2004, Gerald Pfeifer wrote:
>>>> Once we do that, I could easily start bouncing messages which contain
>>>> confidentiality trailers. FWIW, I really hate them.
>> Should we get a steering committee vote on this?
> To be on the safe side, I just sent a message asking whether there are any
> objections. I'm curious how RMS is going to respond [...]
Okay, I think we have clearance to go ahead as you suggested (and start
bouncing messages with confidentiality trailers).
Here is the main remark from the SC dicsussions:
(1) The bounce message will be very clear regarding the reason for
the bounce and point to a page on the GCC (or FSF) website explaining
why it is considered unacceptable. Taken literally they have violated
some privilege to even send to the list and forbidden their email's
inclusion in an archive. Following that argument, we are just doing
what they asked. :) But educating here is a good thing.
I guess referring to http://gcc.gnu.org/lists.html#confidential should be
sufficient.
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2004-03-01 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 15:04 Ian Lance Taylor
2004-01-28 16:17 ` Christopher Faylor
2004-01-28 16:39 ` Gerald Pfeifer
2004-01-28 18:08 ` Christopher Faylor
2004-01-28 18:18 ` Gerald Pfeifer
2004-03-01 22:21 ` Gerald Pfeifer [this message]
2004-01-28 16:28 ` fche
2004-01-28 16:40 ` Ian Lance Taylor
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.58.0403012319030.67370@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).