From: Stefan Seyfried <seife@suse.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Spam on the list
Date: Fri, 15 Jun 2007 17:46:06 +0200 [thread overview]
Message-ID: <20070615154606.GA7548@suse.de> (raw)
In-Reply-To: <c1fa8edf0706150815t2337467fv983969855b0638db@mail.gmail.com>
On Fri, Jun 15, 2007 at 11:15:44AM -0400, Simon wrote:
> Sorry if this has been discussed before, but would it be possible for
> whoever is running the list (Marcel?) to try to moderate the spam so
> that it doesn't reach all of the subscribers?
Even if i am not Marcel, i'll answer this one from my own experience
as a list owner.
Possible: yes
Doable: no.
The list is marked as contact in the kernel MAINTAINERS file, so it needs
to be open to non-subscribers. And real-time moderation of such a list
is a fulltime job. I'd rather have Marcel hacking the code. :-)
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-15 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 15:15 [Bluez-devel] Spam on the list Simon
2007-06-15 15:46 ` Stefan Seyfried [this message]
2007-06-15 15:50 ` Chris Carlin
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=20070615154606.GA7548@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@lists.sourceforge.net \
/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.