From: David Abrahams <dave@boost-consulting.com>
Subject: attachments automatically decompressed before sending?
Date: Mon, 06 Jun 2005 21:40:12 -0400 [thread overview]
Message-ID: <u3brvt05f.fsf@boost-consulting.com> (raw)
I just went through the trouble of compressing an archive before
enclosing it in an email, and what happens when I send but:
bunzip2ing /tmp/mtl4.tar.bz2...done
What is the meaning of this? Is it sending the archive in some
decompressed form? If so, how do I get it to stop?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next reply other threads:[~2005-06-07 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 1:40 David Abrahams [this message]
2005-06-07 6:23 ` Katsumi Yamaoka
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=u3brvt05f.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
/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).