From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Enrico Scholz via lists.openembedded.org"
<enrico.scholz=sigma-chemnitz.de@lists.openembedded.org>
Cc: enrico.scholz@sigma-chemnitz.de,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] npm.bbclass: fix typo in 'fund' config option
Date: Tue, 23 Aug 2022 16:28:48 +0200 [thread overview]
Message-ID: <20220823162848.3468656c@booty> (raw)
In-Reply-To: <20220822111337.1201003-1-enrico.scholz@sigma-chemnitz.de>
Hi Enrico,
On Mon, 22 Aug 2022 13:13:36 +0200
"Enrico Scholz via lists.openembedded.org"
<enrico.scholz=sigma-chemnitz.de@lists.openembedded.org> wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
As you can see above, your sender address is getting mangled. This is
not your fault, it is done by DMARC for anti-phishing, but it makes
applying your patches annoying.
Can you please try to work around that by setting the sendemail.from
parameter in your git config?
You can read the details in this discussion:
https://lists.openembedded.org/g/openembedded-core/message/166515?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Crootfs.py%3A+find+.ko.zst+kernel+modules%2C20%2C2%2C0%2C91453338
Thank you very much!
However you don't need to resend this patch series just for this.
I fixed it manually while applying to my testing branch.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-23 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 11:13 [PATCH 1/2] npm.bbclass: fix typo in 'fund' config option Enrico Scholz
2022-08-22 11:13 ` [PATCH 2/2] npm.bbclass: fix architecture mapping Enrico Scholz
2022-08-23 14:28 ` Luca Ceresoli [this message]
2022-08-23 15:03 ` DKIM compatible maillist setup (was: [OE-core] [PATCH 1/2] npm.bbclass: fix typo in 'fund' config option) Enrico Scholz
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=20220823162848.3468656c@booty \
--to=luca.ceresoli@bootlin.com \
--cc=enrico.scholz=sigma-chemnitz.de@lists.openembedded.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.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