From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Please let me ignore .* files in cache/
Date: 11 Oct 1998 00:26:08 +0200 [thread overview]
Message-ID: <m3hfxcjbpb.fsf@sparky.gnus.org> (raw)
In-Reply-To: Hallvard B Furuseth's message of "08 Oct 1998 09:23:00 +0200"
Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
> BTW, the same problem may exist in some of these:
> gnus-score-score-files-1,
> nnheader-directory-files,
> nnml-generate-nov-databases-1,
> gnus-uu-scan-directory, gnus-uu-directory-files.
> But I expect at least gnus-uu should handle .* files too; I haven't
> checked.
I've now fixed nnml-generate-nov-databases-1 and
nnml-generate-nov-databases-1, but I think the other ones should
probably do the .* files.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-10-10 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-01 19:39 Hallvard B Furuseth
1998-10-02 2:49 ` Lars Magne Ingebrigtsen
1998-10-08 7:23 ` Hallvard B Furuseth
1998-10-10 22:26 ` Lars Magne Ingebrigtsen [this message]
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=m3hfxcjbpb.fsf@sparky.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).