From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: 0.48 doesn't encode my jpegs
Date: 16 Nov 1998 13:27:55 +0000 [thread overview]
Message-ID: <lz4srzdaxw.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: Steinar Bang's message of "16 Nov 1998 14:23:34 +0100"
Steinar Bang <sb@metis.no> writes:
> Hm... well... I edited this message and changed the C-T-E from base64
> to binary, and got up a picture of a little, green, gnome in Gnus with
> TM.
>
> Just pure luck that it survived intact through mail, tho'...
FYI it's a doozer (For those of you who've seen the kiddies programme
Fraggle Rock :)
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next prev parent reply other threads:[~1998-11-16 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 13:17 Lee Willis
1998-11-16 13:23 ` Steinar Bang
1998-11-16 13:27 ` Lee Willis [this message]
1998-11-16 15:01 ` Lars Magne Ingebrigtsen
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=lz4srzdaxw.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).