Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Kaz Kylheku <kaz@zeugmasystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Problem in the usage of mmap command(in directFB)
Date: Fri, 30 Nov 2007 14:11:19 +0000	[thread overview]
Message-ID: <20071130141119.GB26633@linux-mips.org> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C552E3F4@exchange.ZeugmaSystems.local>

On Thu, Nov 29, 2007 at 05:51:26PM -0800, Kaz Kylheku wrote:

> Dear Aptly-Named User, 
> 
> The first clue you need to get is that you shouldn't send MIME-encoded,
> HTML crap to open source mailing lists. 

Linux-mips is configured to bin HTML email.  No prisoners.  It's been
amazingly effective at more than just the spam problem, also zero
maintenance unlike the other approaches to the HTML plague.

  Ralf

      parent reply	other threads:[~2007-11-30 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  5:48 Problem in the usage of mmap command(in directFB) kaka
2007-11-30  1:51 ` Kaz Kylheku
2007-11-30  1:51   ` Kaz Kylheku
2007-11-30 14:11   ` Ralf Baechle [this message]

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=20071130141119.GB26633@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kaz@zeugmasystems.com \
    --cc=linux-mips@linux-mips.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