From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Russell Coker <russell@coker.com.au>,
Soeren Sonnenburg <reiserfs@nn7.de>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Recent spam
Date: 05 Jun 2003 10:52:53 -0400 [thread overview]
Message-ID: <1054824772.23132.140.camel@tiny.suse.com> (raw)
In-Reply-To: <3EDF5618.5090904@namesys.com>
On Thu, 2003-06-05 at 10:39, Hans Reiser wrote:
> flx is moving our webserver and mailserver, and once he has done that I
> will most likely pay the $25. Unfortunately he is distracted by such
> tasks as talking Intel into giving us a 4-way Itanium and splicing a
> cable for it and installing it in its own room because it is noisy,
> talking AMD into giving us some sort of opteron, installing Nina's
> laptop, helping with the problems due to trying to use gcc 3.3, fixing
> the powerbutton on my computer, installing a newer version of xmms that
> can play CDDA out a USB sound device properly, replacing the fans on Mr.
> Demidov's computer so that it can run with the case on it, etc. Giving
> him the additional task of dealing with spamcop is just asinine.
I understand completely ;-) My point is that your last message blamed
anyone using an automated spam reporting tool, when the real problem is
on the reiserfs list side. It's fine if you have other things above it
on the todo list, but please understand where the real cause is.
-chris
next prev parent reply other threads:[~2003-06-05 14:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 6:29 Recent spam Manuel Krause
2003-06-02 6:33 ` Marc-Christian Petersen
2003-06-02 7:24 ` Soeren Sonnenburg
2003-06-02 8:59 ` Russell Coker
2003-06-05 13:26 ` Hans Reiser
2003-06-05 13:39 ` Chris Mason
2003-06-05 14:39 ` Hans Reiser
2003-06-05 14:52 ` Chris Mason [this message]
2003-06-05 19:48 ` Russell Coker
2003-06-06 8:08 ` Hans Reiser
2003-06-06 9:02 ` Soeren Sonnenburg
2003-06-06 14:33 ` Hans Reiser
2003-06-06 14:38 ` Oleg Drokin
2003-06-06 17:42 ` Russell Coker
2003-06-06 22:20 ` Joachim Bremer
2003-06-06 22:34 ` Hans Reiser
2003-06-06 23:05 ` Hans Reiser
2003-06-06 13:01 ` Chris Mason
2003-06-06 13:44 ` Hubert Mantel
2003-06-06 15:30 ` Kristine Diana Daniels
2003-06-06 15:39 ` Chris Mason
2003-06-05 14:57 ` Chris Dukes
2003-06-05 15:11 ` Chris Mason
2003-06-05 15:26 ` Nikita Danilov
2003-06-05 16:30 ` Chris Mason
2003-06-05 15:29 ` Ragnar Kjørstad
2003-06-06 5:31 ` Oleg Drokin
2003-06-05 15:23 ` Hans Reiser
2003-06-05 15:25 ` Hans Reiser
2003-06-05 16:26 ` Chris Mason
2003-06-02 13:02 ` OT: " Asheesh Laroia
2003-06-02 13:06 ` Chris Mason
2003-06-02 13:38 ` Chris Dukes
2003-06-02 13:47 ` Pierre Abbat
2003-06-02 15:54 ` Matthias Andree
2003-06-06 13:09 ` Alexander Lyamin
2003-06-20 19:08 ` John Dalbec
2003-06-08 19:13 ` Alexander Lyamin
2003-06-08 20:05 ` Christophe Saout
2003-06-14 11:03 ` Manuel Krause
2003-07-12 5:44 ` Carl-Daniel Hailfinger
[not found] <no.id>
2003-06-02 7:28 ` The Amazing Dragon
2003-06-05 22:45 ` The Amazing Dragon
-- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:17 Eric Sandeen
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=1054824772.23132.140.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=reiserfs@nn7.de \
--cc=russell@coker.com.au \
/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.