From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Drafts feature-request/bug.
Date: Wed, 11 Sep 2002 18:35:59 +0200 [thread overview]
Message-ID: <vaf7khseb68.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <v94rcwcxcn.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 11 Sep 2002 18:19:52 +0200")
Reiner Steib <4uce.02.r.steib@gmx.net> writes:
> Reading the manual section, I found a typo and saw that there's no
> "summary line" (r.h.s. in <info://gnus/Top>):
Done.
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-09-11 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 23:19 Scott A Crosby
2002-09-11 10:06 ` Kai Großjohann
2002-09-11 10:19 ` Scott A Crosby
2002-09-11 11:09 ` Kai Großjohann
2002-09-11 16:19 ` Reiner Steib
2002-09-11 16:35 ` Kai Großjohann [this message]
2002-09-11 18:44 ` charset problems with gnus-delay (was: Drafts feature-request/bug.) Reiner Steib
2002-09-11 19:41 ` charset problems with gnus-delay Reiner Steib
2002-09-12 9:50 ` charset problems with gnus-delay (was: Drafts feature-request/bug.) Kai Großjohann
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=vaf7khseb68.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).