From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sourceware.org
Subject: Re: Posting from work/university addresses
Date: Sun, 05 Aug 2007 01:58:00 -0000 [thread overview]
Message-ID: <20070805015814.GC21125@cox.net> (raw)
In-Reply-To: <20070805000658.GA29704@ednor.casa.cgf.cx>
On Sat, Aug 04, 2007 at 08:06:58PM -0400, Christopher Faylor wrote:
> On Sat, Aug 04, 2007 at 04:04:23PM -0400, Bob Rossi wrote:
> >On Sat, Aug 04, 2007 at 11:32:44AM -0700, Ian Lance Taylor wrote:
> >>I know you are just trying to be really precise about what is
> >>happening, but, honestly, don't worry: we're free software volunteers
> >>just like you. We're on your side. We won't do anything dumb.
> >
> >I think Eli has a very good point in this matter. It is very easy for
> >a group of talented people to say "trust us, we are doing the correct
> >thing". However, over time, the people change, and other motivating
> >factors can creep in. I agree its best to keep all policy about this
> >matter open. If everyone is doing the right thing, then there is
> >absolutely nothing to hide, right? or perhaps you are afraid that if
> >the spammers know what you are blocking, then they will get good at
> >spamming...
>
> I believe that Ian pointed you to web pages which talk about the spam
> blocking. Here's one in particular:
>
> http://sourceware.org/lists.html#spam
>
> The vast majority of email received at sourceware.org is spam. We have
> obviously been blocking it for quite some time. We also have blocked
> certain individuals who have abused the privilege of sending email to
> the mailing lists.
>
> Remember that you know that the disclaimer block is happening because I
> mentioned it. Suggesting that there may be other motivations for the
> action, that we may be too stupid to do the right thing, that we may
> become untrustworthy over time, or chiding us to be open really seems
> like a pointless exercise to me.
Sure, whatever you say.
next prev parent reply other threads:[~2007-08-05 1:58 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
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 [this message]
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=20070805015814.GC21125@cox.net \
--to=bob_rossi@cox.net \
--cc=gdb@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