From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] URL Encode/Decode Verb
Date: Mon, 19 Aug 2002 17:35:38 +0100 [thread overview]
Message-ID: <016801c2479e$741d0920$6501a8c0@KIKE> (raw)
In-Reply-To: <3D611083.6010808@strakt.com>
> Why not get really into it and handle these MIME atrocities:
>
> From: Mec =?iso-8859-1?q?Givr=E9?= <mec@givre.fr>
can't do anything atm. KFS crashed (no swap - doh) and my fonts got
corrupted. I can't see any text.
Plus I guess that it's not only the fonts.
I do get kernel panics too so I'm getting a bit loathe to trust KFS to stay
alive.
And what with KFS long files names being so clumsy I think it's time to
build a file server.
hmm Anyone know where I can find a Symbios 53C8XX SCSI adapter mail-order
in the uk?
m
---
Outgoing mail is certified as a Virus.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
prev parent reply other threads:[~2002-08-19 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 22:36 matt
2002-08-19 15:36 ` Boyd Roberts
2002-08-19 16:35 ` matt [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='016801c2479e$741d0920$6501a8c0@KIKE' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).