public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "wangmy" <wangmy@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [oe] [meta-oe] [PATCH] capnproto: upgrade 0.10.3 -> 0.10.4
Date: Mon, 17 Apr 2023 09:46:53 +0200	[thread overview]
Message-ID: <20230417094653.4f70d231@booty> (raw)
In-Reply-To: <1681713459-18443-1-git-send-email-wangmy@fujitsu.com>

Hello wangmy,

On Mon, 17 Apr 2023 14:37:35 +0800
"wangmy" <wangmy@fujitsu.com> wrote:

> From: Wang Mingyu <wangmy@fujitsu.com>
> 
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
>  .../capnproto/{capnproto_0.10.3.bb => capnproto_0.10.4.bb}    | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta-oe/recipes-devtools/capnproto/{capnproto_0.10.3.bb => capnproto_0.10.4.bb} (90%)

You have sent several patches today, but they all should be sent to
meta-oe instead of oe-core.

Best regards,
Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      parent reply	other threads:[~2023-04-17  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  6:37 [oe] [meta-oe] [PATCH] capnproto: upgrade 0.10.3 -> 0.10.4 wangmy
2023-04-17  6:37 ` [oe] [meta-oe] [PATCH] ctags: upgrade 6.0.20230402.0 -> 6.0.20230416.0 wangmy
2023-04-17  6:37 ` [oe] [meta-networking] [PATCH] mctp: upgrade 1.0 -> 1.1 wangmy
2023-04-17  6:37 ` [oe] [meta-networking] [PATCH] openvpn: upgrade 2.6.2 -> 2.6.3 wangmy
2023-04-17  6:37 ` [oe] [meta-oe] [PATCH] php: upgrade 8.2.4 -> 8.2.5 wangmy
2023-04-17  7:46 ` 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=20230417094653.4f70d231@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@fujitsu.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