From: Lee Revell <rlrevell@joe-job.com>
To: Eric Shattow <lucent@gmail.com>
Cc: Florian Schlichting <Florian.Schlichting@gmx.de>,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: Ludicrous amount of spam on this list
Date: Sun, 19 Mar 2006 00:10:47 -0500 [thread overview]
Message-ID: <1142745049.4532.9.camel@mindpipe> (raw)
In-Reply-To: <2c746f620603182053y1033befew53e48d29f4741102@mail.gmail.com>
On Sat, 2006-03-18 at 22:53 -0600, Eric Shattow wrote:
> Sorry, it was mentioned that the spam is only 10%; I am experiencing
> 50% or higher spam versus actual content here. FYI. Using filters,
> the bugtracker info is easy enough to sort out.
>
Yes X-Spam-Score.*++++ should help a lot...
> On 3/14/06, Florian Schlichting <Florian.Schlichting@gmx.de> wrote:
> > On Mon, Mar 13, 2006 at 09:25:15PM +0100, Takashi Iwai wrote:
> > > At Mon, 13 Mar 2006 20:05:27 +0000,
> > > Måns Rullgård wrote:
> > > > the bug reporter. I agree that there is a lot of noise from the bug
> > > > tracker on the list. It would help if the subject lines used a
> > > > shorter prefix so the actual subject was visible even when the mail
> > > > reader truncates it to fit the window.
> > >
> > > Yep, agreed that the mail from mantis could be more simplified to be
> > > suitable for ML.
> >
> > And I think it would be useful if bug tracker emails contained a header
> > like References: or In-Reply-To: with the bug number or some such id, so
> > that all emails coming from the same bug report can be grouped in one
> > thread - and read or discarded together, according to interest.
> >
> > Florian
> >
> >
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2 (GNU/Linux)
> >
> > iD8DBQFEFtxK/R0+cAphf/kRAi55AKDlxzh7RnOOVcja4zxRXDTCPHqUIwCghvht
> > MA/ya892LSZdxsi0Dw4Bv44=
> > =IA2D
> > -----END PGP SIGNATURE-----
> >
> >
> >
> �N\x18HS^隊X'u<ڂ.y"\v\x1c*mx%jx.j\a^קvƩXjبȧ\x1emݚv&קv^+jZ{az^hn){h\x18\x1cا+h(mZ\x1fjY\x1awǥrg@y$5Oxḝ\x03n5m\x1dj5^ liׯzYXX liׯzYb,y+^[m+-.ǟ\x1e\x7f+-bا~ږƝz
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-19 5:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 19:03 Ludicrous amount of spam on this list Adrian McMenamin
2006-03-13 19:11 ` Takashi Iwai
2006-03-13 19:18 ` Ismail Donmez
2006-03-13 19:19 ` Adrian McMenamin
2006-03-13 19:32 ` Takashi Iwai
2006-03-13 20:05 ` Måns Rullgård
2006-03-13 20:24 ` Lee Revell
2006-03-13 20:38 ` Takashi Iwai
2006-03-13 20:25 ` Takashi Iwai
2006-03-14 15:07 ` Florian Schlichting
2006-03-19 4:53 ` Eric Shattow
2006-03-19 5:10 ` Lee Revell [this message]
2006-03-19 5:24 ` Lee Revell
2006-03-13 19:21 ` Adrian McMenamin
2006-03-13 19:28 ` Takashi Iwai
2006-03-13 21:28 ` Philip Prindeville
2006-03-13 19:26 ` Lee Revell
2006-03-13 19:42 ` Takashi Iwai
2006-03-13 19:50 ` Lee Revell
2006-03-13 21:30 ` Philip Prindeville
2006-03-13 19:55 ` Måns Rullgård
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=1142745049.4532.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Florian.Schlichting@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=lucent@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox