From: Pavel Roskin <proski@gnu.org>
To: James Ready <jready@mvista.com>, linux-kernel@vger.kernel.org
Subject: MontaVista spam
Date: Tue, 24 Apr 2007 19:33:37 -0400 [thread overview]
Message-ID: <1177457617.18572.36.camel@dv> (raw)
Mr Ready,
If you want to invite Linux kernel developers to your "webinar", please
ask your secretary to send individual invitations. I'm sure you can do
it as the CTO of MontaVista Software.
Please don't pay spammers. Nobody likes them, especially those who are
subjected to spam as a result of their participation in free software
development. MontaVista Software uses some code I helped improve. Is
that your gratitude, Mr Ready?
Spammers lie. I have never subscribed to the "OE Trends Email List".
Do you want your name and the name of your company associated with spam
and lies?
MontaVista Software has contributed some useful code to the kernel.
Your patches are still welcome. But your spam is not.
P.S. My original e-mail was denied by LKML because the mail filter
considered it to be spam. Indeed, the forwarded message must have
triggered quite a lot of spam rules. This time the message it not
forwarded. Instead, it can be found on my website with full headers:
http://80211libre.org/mvistaspam.txt
--
Regards,
Pavel Roskin
reply other threads:[~2007-04-24 23:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1177457617.18572.36.camel@dv \
--to=proski@gnu.org \
--cc=jready@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/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