Gnus development mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <meyering@asic.sc.ti.com>
Cc: ding@ifi.uio.no
Subject: Re: automatically converting 400+ nnmh groups to nnml?
Date: 25 Sep 1996 08:25:41 -0500	[thread overview]
Message-ID: <wpgg246n2ui.fsf@asic.sc.ti.com> (raw)
In-Reply-To: amu@mit.edu's message of 23 Sep 1996 18:36:49 -0400

amu@mit.edu (Aaron M. Ucko) writes:
| Jim Meyering <meyering@asic.sc.ti.com> writes:
| > Any suggestions for automatically converting 400+ nnmh groups to nnml?
| > I'd rather avoid all that typing :-)
| > 
| > Actually they aren't officially nnmh groups as far as Gnus is concerned --
| > I haven't yet told Gnus about them -- they're left over from my days of
| > using e-mh, then Mew (another MH-based Emacs interface).
| 
| Tell Gnus that they're nnml and run the command
| nnml-generate-nov-databases.  This will work because nnml is basically
| nnmh with overview files.

Thanks.
I ended up editing .newsrc.eld and active to do that,
then I ran nnml-generate-nov-databases as you suggested.

Worked like a charm.


           reply	other threads:[~1996-09-25 13:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <udl4tkorh8e.fsf@limekiller.mit.edu>]

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=wpgg246n2ui.fsf@asic.sc.ti.com \
    --to=meyering@asic.sc.ti.com \
    --cc=ding@ifi.uio.no \
    --cc=meyering@na-net.ornl.gov \
    /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).