From: Steinar Bang <sb@metis.no>
Subject: Re: Message forwarding using mime or not using mime
Date: 20 Feb 1999 13:27:46 +0100 [thread overview]
Message-ID: <wh4sohuunx.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Hal Snyder's message of "19 Feb 1999 16:35:43 -0600"
>>>>> Hal Snyder <DrXyzzy@mediaone.net>:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> > 2. Can we have the old style forwarding back as an option?
>>
>> Nope. It felt very, very good to rip out several screenfuls of code
>> that did the old style. :-)
> Does this mean there's no simple way to forward a message and
> intersperse comments with forwarded content? :-(
The best way to do that would anyways be to do a reply to get the
forwarded text quoted, and change the To-field.
prev parent reply other threads:[~1999-02-20 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-17 10:31 Jan Vroonhof
1999-02-19 16:23 ` Lars Magne Ingebrigtsen
1999-02-19 19:35 ` Hrvoje Niksic
1999-02-19 22:35 ` Hal Snyder
1999-02-20 8:18 ` James H. Cloos Jr.
1999-02-20 12:27 ` Steinar Bang [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=wh4sohuunx.fsf@viffer.oslo.metis.no \
--to=sb@metis.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).