From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: fancy-split tracing
Date: Tue, 09 Jul 2002 11:43:57 +0200 [thread overview]
Message-ID: <vafsn2t5j8i.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3u1naqeae.fsf@thneed.na.wrq.com>
Michael Slass <mikesl@wrq.com> writes:
> This only works when the mail first comes in, because that's the only
> time the "* nnmail incoming*" buffer exists, so I can't run
> gnus-summary-respool-trace to see how it's working.
I think when respooling it's " *nnmail move*" or similar.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
parent reply other threads:[~2002-07-09 9:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m3u1naqeae.fsf@thneed.na.wrq.com>]
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=vafsn2t5j8i.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).