From: Michael Lamoureux <lamour@engin.umich.edu>
Cc: ding@ifi.uio.no
Subject: Re: rebuilding .overview
Date: 11 Feb 1997 20:31:08 -0500 [thread overview]
Message-ID: <6ivvi7yq083.fsf@erpland.engin.umich.edu> (raw)
In-Reply-To: Rich Pieri's message of 10 Feb 1997 14:45:37 -0500
"rich" == Rich Pieri <rich.pieri@PrescientTech.com> writes:
>>>>>> "ML" == Michael Lamoureux <lamour@engin.umich.edu> writes:
ML> The best I could come up with was M-x nnml-generate-nov-databases
ML> (which is probably overkill for what I needed...is there a better
ML> way),
rich> You can invoke nnml-generate-nov-databases-1 manually and give
rich> it a directory to build the .overview file within.
Thanks. It just happened again, and this saved me a lot of time.
fyi,
Michael
next prev parent reply other threads:[~1997-02-12 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-10 17:33 Michael Lamoureux
1997-02-10 19:45 ` Rich Pieri
1997-02-12 1:31 ` Michael Lamoureux [this message]
1997-02-11 12:43 ` Lars Magne Ingebrigtsen
1997-02-11 20:21 ` Michael Lamoureux
1997-02-12 8:50 ` 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=6ivvi7yq083.fsf@erpland.engin.umich.edu \
--to=lamour@engin.umich.edu \
--cc=ding@ifi.uio.no \
/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).