From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Attach all files when forwarding in raw mode
Date: Wed, 11 Sep 2024 21:45:53 +0200 [thread overview]
Message-ID: <20240911194553.B8AD62DEB9@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-252@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
There's a merged pull request on the mblaze repository
Attach all files when forwarding in raw mode
https://github.com/leahneukirchen/mblaze/pull/252
Description:
I want to use forwarding with raw messages because it's just easier to work with from the point of view of receivers. The problem is that when "flattening" the message, attachments are lost. This PR extracts them in a temporary folder and adds them to the message to be sent
prev parent reply other threads:[~2024-09-11 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 2:07 [PR PATCH] " rakoo
2023-11-24 12:54 ` [PR PATCH] [Updated] " rakoo
2024-04-24 16:56 ` rakoo
2024-04-24 16:57 ` rakoo
2024-06-06 11:12 ` rakoo
2024-06-06 11:22 ` rakoo
2024-06-06 11:24 ` rakoo
2024-09-11 19:45 ` leahneukirchen [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=20240911194553.B8AD62DEB9@inbox.vuxu.org \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).