From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Parsing of Kai's Emails fails now completlty
Date: Fri, 09 May 2003 18:21:43 +0200 [thread overview]
Message-ID: <m3smro5bxm.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <u8smroa8vu.fsf@gromit.moeb>
On 9 May 2003, Andreas Jaeger <- aj@suse.de wrote:
> Dave Love <d.love@dl.ac.uk> writes:
>> Sorry the rfc2047 changes caused trouble for XEmacs. I thought they
>> had been tested there when I installed them in Emacs originally, but
>> obviously not.
> Everything seems to be fixed now,
It seems so. Very good. Thanks a lot to the one who found the error.
bye
KP
--
"Programs must be written for people to read, and only incidentally
for machines to execute."
-- Abelson & Sussman, SICP (preface to the first edition)
next prev parent reply other threads:[~2003-05-09 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 12:24 Andreas Jaeger
2003-05-04 15:42 ` Xavier Maillard
2003-05-04 19:13 ` Andreas Jaeger
2003-05-06 20:25 ` Xavier Maillard
2003-05-06 22:46 ` Reiner Steib
2003-05-06 23:24 ` Karl Pflästerer
2003-05-08 22:48 ` Dave Love
2003-05-08 23:34 ` Karl Pflästerer
2003-05-11 14:05 ` Dave Love
2003-05-09 7:15 ` Andreas Jaeger
2003-05-09 16:21 ` Karl Pflästerer [this message]
2003-05-07 5:34 ` Andreas Jaeger
2003-05-04 19:50 ` Christoph Garbers
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=m3smro5bxm.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).