From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: compression extensions in Incoming files
Date: 25 Oct 1997 00:33:30 +0200 [thread overview]
Message-ID: <m37mb2kczp.fsf@sparky.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "20 Oct 1997 17:14:23 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> Was the problem with Incoming files accidentally getting "valid"
> compression extensions (.Z, .gz) fixed? The 5.2 and 5.4 ChangeLogs do not
> mention it.
No, this is the first I've heard of the problem. nnmail simply uses
`make-temp-name' (with some possible x'es appended), so if there's a
bug here, it must be in that function.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
parent reply other threads:[~1997-10-24 22:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <x7201gjfww.fsf@peorth.gweep.net>]
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=m37mb2kczp.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).