From: Marcel Holtmann <marcel@holtmann.org>
To: thomas.kear@gmail.com,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] aaaaaargh spam
Date: Thu, 15 Feb 2007 09:24:30 +0100 [thread overview]
Message-ID: <1171527870.28302.22.camel@violet> (raw)
In-Reply-To: <200702151229.33228.thomas.kear@gmail.com>
Hi Thomas,
> > Is there any way sourceforge can curtail all this bloody spam on the list?
>
> Cue the 5th (or so) discussion about this topic in just a few short months.
> Usually the direction these threads take is toward list posting being closed
> so only list subscribers can post to the list. Hasn't happened yet though.
to make this clear once and for all. Write to the Sourceforge guys and
complain about the spam. I have no way to add spam filters to the
mailing list.
The bluez-users mailing list is now closed for subscribers, but for
bluez-devel this is not an option. This mailing list is listed in the
MAINTAINERS file of the Linux kernel and meant to be an open mailing
list.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-15 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 23:00 [Bluez-devel] aaaaaargh spam Mike Hodson
2007-02-14 23:29 ` Thomas Kear
2007-02-15 8:24 ` Marcel Holtmann [this message]
2007-02-15 9:16 ` Mike Hodson
2007-02-15 22:34 ` Kinney Baughman
2007-02-16 3:51 ` Andrew Kohlsmith
2007-02-16 8:31 ` Marcel Holtmann
2007-02-16 4:06 ` Kelly Price
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=1171527870.28302.22.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=thomas.kear@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.