From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: dewar@adacore.com, Ian Lance Taylor <iant@google.com>,
b07584@freescale.com, rgetz@blackfin.uclinux.org,
jimb@codesourcery.com, gdb@sourceware.org,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Posting from work/university addresses
Date: Sun, 05 Aug 2007 00:03:00 -0000 [thread overview]
Message-ID: <20070805000352.GA11072@ednor.casa.cgf.cx> (raw)
In-Reply-To: <u4pjfb0c7.fsf@gnu.org>
On Sat, Aug 04, 2007 at 09:50:48PM +0300, Eli Zaretskii wrote:
>>From: Ian Lance Taylor
>>Date: 04 Aug 2007 11:32:44 -0700
>>
>>As far as I can tell, you are requesting that we not do anything dumb,
>
>No, that's not it. My problem is that I don't see the motivation for
>rejecting such messages spelled out anywhere. The URL you mentioned
>_advises_ to do something, but, AFAIU, there's some policy issues
>involved here, which are not explained anywhere.
Actually, the words politely requires that confidentiality notices not
be included. Since that was the best we could do until recently we
relied, unsuccessfully, on people to do the right thing. I've been
promising people for years that I'd modify the spam software enforce the
policy and a recent discussion on the gcc channel prodded me into taking
action.
>>we're free software volunteers just like you. We're on your side. We
>>won't do anything dumb.
>
>Isn't this a matter of policy of Red Hat (or some other organization)?
>I do trust you, but I don't know about organizations.
AFAIK, this has nothing to do with Red Hat.
cgf
next prev parent reply other threads:[~2007-08-05 0:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 8:14 Why does gdb implement 'next' command with a series of "vCont;s"? congli
2007-07-30 22:12 ` Posting from work/university addresses Jim Blandy
2007-07-31 0:08 ` Anmol P. Paralkar
2007-07-31 1:08 ` Christopher Faylor
2007-08-02 16:58 ` Robin Getz
2007-08-02 17:12 ` Robert Dewar
2007-08-02 17:42 ` Robin Getz
2007-08-02 18:09 ` Ian Lance Taylor
2007-08-04 17:36 ` Eric Weddington
2007-08-02 18:23 ` Jim Blandy
2007-08-02 18:34 ` Christopher Faylor
2007-08-03 12:05 ` Eli Zaretskii
2007-08-03 14:27 ` Christopher Faylor
2007-08-03 14:39 ` Ian Lance Taylor
2007-08-03 17:10 ` Eli Zaretskii
2007-08-03 23:11 ` Christopher Faylor
2007-08-04 8:41 ` Eli Zaretskii
2007-08-04 18:36 ` Ian Lance Taylor
2007-08-04 18:51 ` Eli Zaretskii
2007-08-05 0:03 ` Christopher Faylor [this message]
2007-08-05 3:51 ` Robin Getz
2007-08-05 5:07 ` Christopher Faylor
2007-08-05 12:03 ` Robert Dewar
2007-08-05 18:27 ` Christopher Faylor
2007-08-06 6:53 ` Eli Zaretskii
2007-08-06 14:04 ` Ian Lance Taylor
2007-08-06 14:22 ` Eli Zaretskii
2007-08-04 20:04 ` Bob Rossi
2007-08-05 0:06 ` Christopher Faylor
2007-08-05 1:58 ` Bob Rossi
2007-08-05 3:13 ` Eli Zaretskii
2007-08-05 4:33 ` Christopher Faylor
2007-08-06 14:07 ` Ian Lance Taylor
2007-07-31 7:59 ` Wenbo Yang
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=20070805000352.GA11072@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=b07584@freescale.com \
--cc=dewar@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=jimb@codesourcery.com \
--cc=rgetz@blackfin.uclinux.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