From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Random spaces in the subject
Date: Fri, 02 Jan 2004 23:43:24 +0100 [thread overview]
Message-ID: <m3ekui3rar.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2brpmq8ip.fsf@nkpbook-invalid.cs.caltech.edu>
Nevin Kapur <nkapur@cs.caltech.edu> writes:
> I don't know how to check the overview data.
Enter the group with `RET', and then go to the " *nntpd*" (note
leading space) buffer and look what's in there.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-01-02 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 2:48 Nevin Kapur
2004-01-02 22:06 ` Lars Magne Ingebrigtsen
2004-01-02 22:19 ` Reiner Steib
2004-01-02 22:40 ` Nevin Kapur
2004-01-02 22:43 ` Lars Magne Ingebrigtsen [this message]
2004-01-02 23:09 ` Nevin Kapur
2004-01-02 22:53 ` Russ Allbery
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=m3ekui3rar.fsf@quimbies.gnus.org \
--to=larsi@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).