Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: \201 gone again?
Date: Wed, 19 Feb 2003 21:43:12 +0100	[thread overview]
Message-ID: <v9u1f0huhr.fsf@marauder.physik.uni-ulm.de> (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")

On Wed, Feb 19 2003, Kai Großjohann wrote:

> It seems that there was a fix for the \201 bug today or yesterday.
> Or am I dreaming?

Handa-san (is this correct?) fixed it on Monday [1].

Kai, you should read emacs-devel when using CVS-Emacs, SCNR. ;-)

Bye, Reiner.

[1] <news:200302170035.JAA15102@etlken.m17n.org>
    <URL: http://article.gmane.org/gmane.emacs.devel/11690>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



  parent reply	other threads:[~2003-02-19 20:43 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
2003-02-19 20:43 ` Reiner Steib [this message]
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=v9u1f0huhr.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.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).