public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yang Xu (徐扬)" <Yang.Xu@mediatek.com>
To: "yang.xu=mediatek.com@lists.openembedded.org"
	<yang.xu=mediatek.com@lists.openembedded.org>,
	"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [PATCH v2] openssl: set package level PERL5LIB
Date: Tue, 25 Apr 2023 06:04:06 +0000	[thread overview]
Message-ID: <5035080e48ce2ada7911332910175e30e8eadbdb.camel@mediatek.com> (raw)
In-Reply-To: <20230420104355.68722b88@booty>

Dear Sirs,

Sorry, please NOT accept this patch because I found it will break its
own sstate cache.

I will found other solution for this openssl/perl co-work issue.

On Thu, 2023-04-20 at 10:43 +0200, Luca Ceresoli wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> Hello Yang,
> 
> thanks for you patch. However there is an issue with your e-mail, see
> below
> 
> On Thu, 20 Apr 2023 06:30:34 +0000
> "Yang Xu via lists.openembedded.org"
> <yang.xu=mediatek.com@lists.openembedded.org> wrote:
>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> As you can see your sender address has been mangled, and as a result
> the patch is rejected by the the openembedded git server. This is not
> your fault, but we need you to modify your git configuration to
> prevent
> this from happening in the future. Have a look at the wiki for more
> info and how to solve that:
> 
> 
https://urldefense.com/v3/__https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded*Fixing_your_From_identity__;Iw!!CTRNKA9wMg0ARbw!mqd2E9hIGSyXX1IuHHAsZENlRGaglvctXM4n_aGmmPesGsE7KMIxiBwRhAo_7H7IP7fVwq1ICYPKoQVXgz6U1ZFvnQ$
> 
> I'm taking your patch for testing on the autobuilders, fixing it
> manually so you don't need to resend it.
> 
> Best regards,
> Luca
> 
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> 
https://urldefense.com/v3/__https://bootlin.com__;!!CTRNKA9wMg0ARbw!mqd2E9hIGSyXX1IuHHAsZENlRGaglvctXM4n_aGmmPesGsE7KMIxiBwRhAo_7H7IP7fVwq1ICYPKoQVXgz6LUphplw$

      reply	other threads:[~2023-04-25  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  6:30 [PATCH v2] openssl: set package level PERL5LIB Yang Xu
2023-04-20  8:43 ` [OE-core] " Luca Ceresoli
2023-04-25  6:04   ` Yang Xu (徐扬) [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=5035080e48ce2ada7911332910175e30e8eadbdb.camel@mediatek.com \
    --to=yang.xu@mediatek.com \
    --cc=alex.kanavin@gmail.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yang.xu=mediatek.com@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