From: Henrik Enberg <henrik@enberg.org>
Cc: ding@gnus.org
Subject: Re: \201 gone again?
Date: Wed, 19 Feb 2003 21:38:05 +0100 [thread overview]
Message-ID: <87lm0crope.fsf@enberg.org> (raw)
In-Reply-To: <84el64jcne.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Wed, 19 Feb 2003 20:25:41 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> It seems that there was a fix for the \201 bug today or yesterday.
> Or am I dreaming?
They're gone for me too.
next prev parent reply other threads:[~2003-02-19 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 19:25 Kai Großjohann
2003-02-19 20:38 ` Henrik Enberg [this message]
2003-02-19 20:43 ` Reiner Steib
2003-02-20 9:59 ` Kai Großjohann
2003-02-19 20:45 ` Frank Schmitt
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=87lm0crope.fsf@enberg.org \
--to=henrik@enberg.org \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).