From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: sending MIME attachments with Pterodactyl
Date: 08 Feb 1999 10:57:37 +0100 [thread overview]
Message-ID: <vafvhhdcj5a.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: lewst@yahoo.com's message of "Sun, 7 Feb 1999 20:38:30 -0800 (PST)"
lewst@yahoo.com writes:
> Okay, thanks. I suggest adding this command to the "Message"
> menu, and also to the documentation somewhere (unless already
> there).
The MIME composition thing will change quite a bit in the future, C-c
C-a was just a stopgap solution.
kai
--
I like _\bb_\bo_\bt_\bh kinds of music.
next prev parent reply other threads:[~1999-02-08 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-08 4:38 lewst
1999-02-08 9:57 ` Kai.Grossjohann [this message]
1999-02-08 15:30 ` Hrvoje Niksic
1999-02-09 16:07 ` Lars Magne Ingebrigtsen
1999-02-09 16:06 ` Lars Magne Ingebrigtsen
1999-02-10 9:15 ` Kai.Grossjohann
1999-02-11 4:10 ` Lars Magne Ingebrigtsen
1999-02-11 9:03 ` Kai.Grossjohann
1999-02-09 16:05 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1999-02-08 4:17 lewst
1999-02-08 4:23 ` Carsten Leonhardt
1999-02-08 4:24 ` Chris Tessone
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=vafvhhdcj5a.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).