From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Christopher Faylor <cgf@redhat.com>,
gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [ADMINISTRIVIA] "gdb-bugs at sources dot redhat dot com" gatewayed to "bug-gdb at gnu dot org"
Date: Tue, 09 Apr 2002 05:52:00 -0000 [thread overview]
Message-ID: <200204091251.NAA29257@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 09 Apr 2002 00:04:26 EDT." <3CB2684A.9080300@cygnus.com>
> In a word. Bliss!
>
> Andrew
>
> > I've recently gatewayed the apparently defunct gdb-bugs mailing list on
> > sourceware to bug-gdb at gnu.
> >
> > This means that messages to gdb-bugs will go to bug-gdb and vice versa.
> > One notable exception is that most spam sent to bug-gdb won't make it to
> > gdb-bugs thanks to the spam blocking software running on
> > sources.redhat.com.
> >
> > That's my primary motivation for effecting this gateway. As I was in
> > the process of typing this message, sourceware blocked four pieces of
> > spam from bug-gdb. So, I guess that part works.
> >
> > This has been in operation for a while now so I think it is safe to
> > conclude that it is working. Feel free to subscribe by sending email to
> >
> > gdb-bugs-subscribe at sources dot redhat dot com
But doesn't this mean that everything we now post to gdb-bugs will get
splatted onto usenet, where all those spam-bots will start garnering email
addresses?
R.
next prev parent reply other threads:[~2002-04-09 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 19:32 Christopher Faylor
2002-04-08 21:04 ` Andrew Cagney
2002-04-09 5:52 ` Richard Earnshaw [this message]
2002-04-09 6:08 ` Christopher Faylor
2002-04-09 6:20 ` Richard Earnshaw
2002-04-09 6:25 ` Christopher Faylor
2002-04-09 6:32 ` Richard Earnshaw
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=200204091251.NAA29257@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=cgf@redhat.com \
--cc=gdb@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