From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH edk2-firmware] add patch to work around older guest kernel bug
Date: Wed, 7 Jun 2023 12:25:15 +0200 [thread overview]
Message-ID: <b57c9397-9682-6535-90a4-9adf241dd0a9@proxmox.com> (raw)
In-Reply-To: <c72e637b-2e92-2ff5-0bc5-0c99d55b2ec8@proxmox.com>
Am 07/06/2023 um 12:12 schrieb Fiona Ebner:
>> Hmm, it's correct in my repository and in the formatted patch, but not
>> here in the mail anymore. Do I need to specify something special with
>> git send-email?
>>
> I asked Stoiko and sending the mail to him or myself directly works as
> intended, so it might be an issue with mailman.
>
> If anybody wants to send an edk2-firmware patch until there is time to
> look at the issue more closely, he said that the
> --transfer-encoding=base64 option for git send-email might be worth a shot.
And possibly the `--keep-cr` option of `git am`
prev parent reply other threads:[~2023-06-07 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 7:43 [pve-devel] " Fiona Ebner
2023-06-06 14:26 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-07 9:04 ` Fiona Ebner
2023-06-07 10:12 ` Fiona Ebner
2023-06-07 10:25 ` Thomas Lamprecht [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=b57c9397-9682-6535-90a4-9adf241dd0a9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox