From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Robert Pluim <rpluim@gmail.com>, 45631@debbugs.gnu.org
Subject: bug#45631: 27.1; regression: message-forward-ignored-headers no longer applies when forwarding as MIME
Date: Tue, 19 Jan 2021 11:19:58 -0500 [thread overview]
Message-ID: <87r1mgj3v5.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87lfcpsjr1.fsf@gnus.org>
On Tue 2021-01-19 04:12:02 +0100, Lars Ingebrigtsen wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>> Either or both (or neither) of these variables might be applied in any
>> of the three scenarios. If both are applied, i have no idea which order
>> they are applied in, so applying both is probably not a great idea. ☹
>
> Both are applied.
In all cases? I think neither are applied in case 3, right?
At any rate, if they're typically applied in tandem, it seems like their
help text should probably refer to each other -- this discussion is the
first place i've learned about message-forward-included-headers :/
> We can't change when they're applied, because that will break people's
> setups. So we have to introduce a new variable for 3).
In case 3, neither are currently applied.
The only thing i'm asking for is to apply *only* the blocklist in case
3. What setups will that break?
--dkg
next prev parent reply other threads:[~2021-01-19 16:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 17:12 bug#45631: 27.1; regression: message-forward-ignored-headers no longer applies when forwarding as MIME Daniel Kahn Gillmor
2021-01-05 13:06 ` Robert Pluim
2021-01-05 23:25 ` Daniel Kahn Gillmor
2021-01-06 10:31 ` Robert Pluim
2021-01-10 15:18 ` Lars Ingebrigtsen
2021-01-10 17:25 ` Eli Zaretskii
2021-01-11 15:04 ` Lars Ingebrigtsen
2021-01-10 21:41 ` Daniel Kahn Gillmor
2021-01-11 15:09 ` Lars Ingebrigtsen
2021-01-12 14:57 ` Daniel Kahn Gillmor
2021-01-13 9:25 ` Robert Pluim
2021-01-13 17:35 ` Daniel Kahn Gillmor
2021-01-18 15:50 ` Lars Ingebrigtsen
2021-01-18 17:43 ` Daniel Kahn Gillmor
2021-01-19 3:12 ` Lars Ingebrigtsen
2021-01-19 16:19 ` Daniel Kahn Gillmor [this message]
2021-01-20 16:17 ` Lars Ingebrigtsen
2021-01-20 19:31 ` Daniel Kahn Gillmor
2021-01-21 15:46 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1mgj3v5.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=45631@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).