From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: dfsd df <tomcs163@yahoo.com.cn>, linux-mips@linux-mips.org
Subject: Re: Some questions about kernel tailoring
Date: Thu, 31 Mar 2005 17:09:42 +0100 [thread overview]
Message-ID: <20050331160942.GI27952@linux-mips.org> (raw)
In-Reply-To: <424B2621.20006@longlandclan.hopto.org>
On Thu, Mar 31, 2005 at 08:20:17AM +1000, Stuart Longland wrote:
> (PS... Please refrain from HTML email on this list)
The list is configured to reject HTML email. But - the filter didn't
detect this broken use of HTML.
Ralf
next prev parent reply other threads:[~2005-03-31 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 7:37 Some questions about kernel tailoring dfsd df
2005-03-30 22:20 ` Stuart Longland
2005-03-31 16:09 ` Ralf Baechle DL5RB [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-31 1:49 dfsd df
2005-03-31 3:49 ` Stuart Longland
2005-03-31 9:41 dfsd df
2005-03-31 22:06 ` Stuart Longland
2005-04-01 0:29 ` Wolfgang Denk
2005-04-01 1:08 dfsd df
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=20050331160942.GI27952@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=stuartl@longlandclan.hopto.org \
--cc=tomcs163@yahoo.com.cn \
/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