From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Message forwarding using mime or not using mime
Date: 19 Feb 1999 17:23:34 +0100 [thread overview]
Message-ID: <m3aeyapdkp.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Jan Vroonhof's message of "17 Feb 1999 11:31:36 +0100"
Jan Vroonhof <vroonhof@math.ethz.ch> writes:
> 1. Now that message-forward does not directly use the " *gnus
> forward*" buffer, but instead just inserts some MML stuff to
> include it when sending shouldn't the " *gnus forward*" buffer be
> made unique?, i.e. What happens when I forward another article
> before sending of the first one?
Yup. Fix in Pterodactyl Gnus v0.77.
> 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. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-02-19 16:23 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 [this message]
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
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=m3aeyapdkp.fsf@quimbies.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).