Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] aaaaaargh spam
Date: Fri, 16 Feb 2007 09:31:35 +0100	[thread overview]
Message-ID: <1171614695.7583.39.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200702152251.21242.akohlsmith-bluez@benshaw.com>

Hi Andrew,

> > 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.
> 
> I'm not a mailman expert, but I'd be surprised if there isn't a "confirm your 
> post if you're a nonsubscriber" option somewhere...

the whole point is to have this mailing list open, because non-BlueZ
people will forward kernel related stuff. It will stay open.

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

  reply	other threads:[~2007-02-16  8:31 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
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 [this message]
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=1171614695.7583.39.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox