From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: maanyagoenka@microsoft.com
Cc: "maanyagoenka@linux.microsoft.com"
<maanyagoenka@linux.microsoft.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
paul.eggleton@microsoft.com
Subject: Re: [OE-core] [PATCH] create-spdx: fix config build by adding dependency to enable reruns
Date: Wed, 18 Jan 2023 11:06:01 +0100 [thread overview]
Message-ID: <20230118110601.7d497d8f@booty> (raw)
In-Reply-To: <IA1PR21MB3499E02B1F7C9AD4D0F389C9D3C69@IA1PR21MB3499.namprd21.prod.outlook.com>
Hello Maanya,
On Tue, 17 Jan 2023 18:02:52 +0000
"Maanya Goenka via lists.openembedded.org"
<maanyagoenka=microsoft.com@lists.openembedded.org> wrote:
> Also, signed off by Paul Eggleton: paul.eggleton@microsoft.com
> ________________________________
> From: maanyagoenka@linux.microsoft.com <maanyagoenka@linux.microsoft.com>
> Sent: Tuesday, January 17, 2023 10:01 AM
> To: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>
> Cc: Maanya Goenka <maanyagoenka@linux.microsoft.com>; Maanya Goenka <maanyagoenka@microsoft.com>
> Subject: [PATCH] create-spdx: fix config build by adding dependency to enable reruns
Here you seem to be replying to a patch, but the original patch does
not appear neither in my inbox nor in the archives (I checked on
lore.kernel.org).
Can you send the patch again? A "[PATCH][RESEND]" tag would be OK I
guess.
Thank you!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-01-18 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1673978504-5453-1-git-send-email-maanyagoenka@linux.microsoft.com>
2023-01-17 18:02 ` [PATCH] create-spdx: fix config build by adding dependency to enable reruns Maanya Goenka
2023-01-18 10:06 ` Luca Ceresoli [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=20230118110601.7d497d8f@booty \
--to=luca.ceresoli@bootlin.com \
--cc=maanyagoenka@linux.microsoft.com \
--cc=maanyagoenka@microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.