From: Ian Lance Taylor <iant@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org, dewar@adacore.com, b07584@freescale.com,
rgetz@blackfin.uclinux.org, jimb@codesourcery.com
Subject: Re: Posting from work/university addresses
Date: Sat, 04 Aug 2007 18:36:00 -0000 [thread overview]
Message-ID: <m3sl6zup4j.fsf@localhost.localdomain> (raw)
In-Reply-To: <ubqdnbsmd.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Since the regexps mentioned above were not disclosed, and the URL Ian
> mentioned doesn't say anything about rejecting messages, and doesn't
> define precisely which kinds of text will be a reason for rejection, I
> can only hope that the filters will reject only messages that could
> present legal problems for sourceware, not, for example, the kind of
> text mentioned here:
As far as I can tell, you are requesting that we not do anything dumb,
such as, for example, blocking messages which are not spam and which
do not violate the documented mailing list guidelines. That is a
reasonable request. I promise we won't do anything dumb.
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.
Ian
next prev parent reply other threads:[~2007-08-04 18:36 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 [this message]
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
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=m3sl6zup4j.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=b07584@freescale.com \
--cc=dewar@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--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