From: Andy Eskilsson <flognat@fukt.hk-r.se>
Cc: ding@ifi.uio.no
Subject: Re: compressed nnfolder archives
Date: 24 Jul 1996 07:51:40 +0200 [thread overview]
Message-ID: <lvvifefbbn.fsf@claymore.fukt.hk-r.se> (raw)
In-Reply-To: Mark Borges's message of 23 Jul 1996 15:27:31 -0600
/Mark Borges <mdb@cdc.noaa.gov> wrote:
|
| jka-compr relies on the extension, but crypt++ does not. It peeks
| inside the file and uses a magic number technique. I've used crypt++
| to automagically decode many gzip'd files wø the `.gz'filename
| extension.
Hmm I think I switched from crypt++ to jka-compr when crypt++ didn't
work too goo good together with rmail (yep it was those old days), I
think it was that crypt++ couldn't handle appending to files.
Is it something to be worried about in gnus?
Åndy
--
Hi I am an alien .sig, and at the moment I am having sex to your
mind, by looking at your smile I can see that you like it.
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.fukt.hk-r.se/~flognat/mail/> for more info.
next prev parent reply other threads:[~1996-07-24 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-23 6:30 Erik Selberg
[not found] ` <x7viff9jex.fsf@unilab.dfci.harvard.edu>
1996-07-23 21:27 ` Mark Borges
1996-07-24 5:51 ` Andy Eskilsson [this message]
1996-07-24 13:34 ` Richard Pieri
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=lvvifefbbn.fsf@claymore.fukt.hk-r.se \
--to=flognat@fukt.hk-r.se \
--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).