From: Harald Milz <milz@seneca.muc.de>
To: cpufreq@www.linux.org.uk
Subject: Re: Spam coming from the list
Date: Mon, 27 Sep 2004 17:04:46 +0200 (CEST) [thread overview]
Message-ID: <20040927150446.0EEC540AA8@nathan.muc.de> (raw)
In-Reply-To: 20040927143930.GA6561@redhat.com
Dave Jones <davej@redhat.com> wrote:
> People should not have to be subscribed to a list just to report a bug.
> It's annoying as hell every time I come up with random patches, dig
> out the contact address out of MAINTAINERS, and send patches to get
> a 'you aren't subscribed yadayada' email back.
Understand. The question is which evil is the bigger one ... It's not as if
spam were less annoying ;-)
--
Nothing recedes like success.
-- Walter Winchell
next prev parent reply other threads:[~2004-09-27 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 14:45 Spam coming from the list Julio De Gregorio
2004-09-26 15:29 ` Russell King
2004-09-26 16:24 ` aeriksson
2004-09-26 20:51 ` Russell King
2004-09-27 11:51 ` Frank Mehnert
2004-09-27 12:16 ` David Pottage
2004-09-27 14:24 ` Harald Milz
2004-09-27 14:39 ` Dave Jones
2004-09-27 15:04 ` Harald Milz [this message]
2004-09-27 21:39 ` Francesco Poli
2004-09-27 20:35 ` aeriksson
2004-09-27 20:50 ` Russell King
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=20040927150446.0EEC540AA8@nathan.muc.de \
--to=milz@seneca.muc.de \
--cc=cpufreq@www.linux.org.uk \
/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