From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Possible bug in nnml code
Date: Sat, 07 Dec 2002 15:48:15 +0100 [thread overview]
Message-ID: <84vg25rikw.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m2adjiub2q.fsf@tnuctip.rychter.com>
Jan Rychter <jan@rychter.com> writes:
> The general idea is to:
Sounds like the right thing to do.
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-07 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2ptsgvyfq.fsf@tnuctip.rychter.com>
2002-12-06 13:35 ` Kai Großjohann
[not found] ` <m2adjiub2q.fsf@tnuctip.rychter.com>
2002-12-06 21:23 ` Ted Zlatanov
2002-12-07 14:48 ` Kai Großjohann [this message]
2002-12-28 18:31 ` 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=84vg25rikw.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.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).