From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] spam controls
Date: Sat, 17 Feb 2007 11:39:41 +0100 [thread overview]
Message-ID: <1171708781.27519.5.camel@violet> (raw)
In-Reply-To: <7ff566830702161809g3549664aob33b7d2b9fc2a7ac@mail.gmail.com>
Hi Kelly,
> > Because this list is in the MAINTAINERS file of the linux kernel, listed
> > as contact for the bluez subsystem:
> >
> > BLUETOOTH SUBSYSTEM
> > P: Marcel Holtmann
> > M: marcel@holtmann.org
> > P: Maxim Krasnyansky
> > M: maxk@qualcomm.com
> > L: bluez-devel@lists.sf.net
> > W: http://bluez.sf.net
> > W: http://www.bluez.org
> > W: http://www.holtmann.org/linux/bluetooth/
> > T: git kernel.org:/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git
> > S: Maintained
> >
>
> Wait a min... from the kernel sources MAINTAINERS file (usually
> located in /usr/src/linux/):
>
> **BEGIN QUOTE**
> P: Person
> M: Mail patches to
> L: Mailing list that is relevant to this area
> W: Web-page with status/info
> T: SCM tree type and location. Type is one of: git, hg, quilt.
> S: Status, one of the following:
> **END QUOTE**
>
> If I'm reading the MAINTAINERS file correctly, the persons of contact
> are Marcel and Maxim. The development list is recognized as such, and
> the websites are listed. There is no requirement that the list be
> open for everyone and their mother to post to, and it's only common
> sense that subscription information be made availible (which it is on
> the web site, it's how I subscribed).
>
> I'm of the position that if you're looking to send in a patch, you at
> least send it to Marcel and Maxim; you more likely join the list and
> send it through there. The most intelligent would check the archives
> to see if it's been fixed already before getting involved. Only an
> moron would spam all three email addresses with a patch; only an idiot
> would spam dribble to all three. Unfortunately, spammers have been
> observed to be idiots.
that is wrong. People CC the mailing list when they do changes and there
is no need that people like Andrew Morton, Adrian Bunk etc. have to
subscribe to it first. And I want it this way. Period.
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-17 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 19:19 [Bluez-devel] spam controls John H.
2007-02-16 19:30 ` Stefan Behlert
2007-02-16 21:04 ` Marcel Holtmann
2007-02-16 19:30 ` Stefan Seyfried
2007-02-16 19:35 ` John H.
2007-02-17 2:09 ` Kelly Price
2007-02-17 10:39 ` Marcel Holtmann [this message]
2007-02-17 17:21 ` 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=1171708781.27519.5.camel@violet \
--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 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.