From: Matt Pharr <mmp@graphics.stanford.edu>
Subject: Re: gnus-summary-mail-forward - included headers
Date: 09 Nov 1999 09:47:13 -0800 [thread overview]
Message-ID: <kh0hfivy2u6.fsf@abuffer.stanford.edu> (raw)
In-Reply-To: Dan Christensen's message of "Tue, 09 Nov 1999 01:55:52 -0500"
Dan Christensen <jdc@jhu.edu> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> >
> > > Trimming the headers by hand is a pain, and would be better if
> > > automated, as it was before.
> >
> > I've now added message-ignored-forward-headers.
>
> I don't see this in the source or in the documentation, although
> I do see a Changelog entry. What's up?
Actually, it's "message-forward-ignored-headers"
-matt
--
Matt Pharr mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>
next prev parent reply other threads:[~1999-11-09 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-14 16:24 Jim Davidson
1999-09-14 16:51 ` Kai Großjohann
1999-09-14 18:20 ` Toby Speight
1999-09-25 9:18 ` Lars Magne Ingebrigtsen
1999-09-30 23:35 ` message-ignored-forward-headers (was: Re: gnus-summary-mail-forward - included headers) Thomas Hungenberg
1999-10-01 17:33 ` Jack Vinson
1999-10-08 16:52 ` Jim Davidson
1999-10-08 18:41 ` Jack Vinson
1999-11-06 2:13 ` Lars Magne Ingebrigtsen
1999-11-08 22:31 ` [patch] message-forward-as-mime (was: Re: message-ignored-forward-headers (was: Re: gnus-summary-mail-forward - included headers)) Matt Pharr
1999-11-11 19:32 ` Toni Drabik
1999-10-04 22:51 ` gnus-summary-mail-forward - included headers François Pinard
1999-10-05 8:22 ` Kai Großjohann
1999-10-05 14:15 ` Hrvoje Niksic
1999-11-06 3:15 ` Lars Magne Ingebrigtsen
1999-11-09 6:55 ` Dan Christensen
1999-11-09 17:47 ` Matt Pharr [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 9:59 Thomas Hungenberg
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=kh0hfivy2u6.fsf@abuffer.stanford.edu \
--to=mmp@graphics.stanford.edu \
/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).