From: Matt Ranney <mjr@ranney.com>
Subject: Re: nnfolder problems
Date: 17 Oct 2001 08:29:11 -0700 [thread overview]
Message-ID: <m3adyqp9o8.fsf@wacky.ranney.com> (raw)
In-Reply-To: <vafelo2eb69.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann) writes:
> The easiest way to do that for a couple of files is using `G f'. Then
> you'll get read-only groups.
The thing is, I have like 50 of these fkles, and new ones are showing
up every week or so.
Either way, I'm guessing its pretty hard.
--
Matt Ranney - mjr@ranney.com
next prev parent reply other threads:[~2001-10-17 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 1:10 Matt Ranney
2001-10-17 11:52 ` Kai Großjohann
2001-10-17 15:29 ` Matt Ranney [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-05-18 4: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=m3adyqp9o8.fsf@wacky.ranney.com \
--to=mjr@ranney.com \
/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).