Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 02/19] package_rpm: remove support for DIRFILES
Date: Mon, 03 Jun 2024 05:11:23 -0700	[thread overview]
Message-ID: <30049.1717416683403790176@lists.openembedded.org> (raw)
In-Reply-To: <20240419121945.1920944-2-alex@linutronix.de>

As i see it is merged only for master branch of poky repo. Will it be merged to scarthgap branch also?

It seems to me i have an issue which can be solved in scarthgap via this patch:
https://github.com/DynamicDevices/meta-mono/pull/224#issuecomment-2144017190


  parent reply	other threads:[~2024-06-03 12:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 12:19 [PATCH 01/19] liba52: remove the recipe Alexander Kanavin
2024-04-19 12:19 ` [PATCH 02/19] package_rpm: remove support for DIRFILES Alexander Kanavin
2024-04-19 16:38   ` [OE-core] " Ross Burton
2024-04-19 16:40     ` Ross Burton
2024-06-03 12:11   ` Livius [this message]
2024-06-03 14:12     ` Alexander Kanavin
2024-06-04  8:53       ` Livius
2024-06-04  8:54         ` Livius
2024-04-19 12:19 ` [PATCH 03/19] serf: mark patch as inappropriate for upstream submission Alexander Kanavin
2024-04-19 12:19 ` [PATCH 04/19] swig: merge .inc into .bb Alexander Kanavin
2024-04-20 12:11   ` [OE-core] " Richard Purdie
2024-04-20 17:58     ` Alexander Kanavin
2024-04-22 10:46     ` Alexander Kanavin
2024-04-19 12:19 ` [PATCH 05/19] swig: convert from autotools to cmake Alexander Kanavin
2024-04-19 12:19 ` [PATCH 06/19] kea: remove unnecessary reproducibility patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 07/19] expect: mark patches as Inactive-Upstream Alexander Kanavin
2024-04-19 12:19 ` [PATCH 08/19] apr: submit 0001-Add-option-to-disable-timed-dependant-tests.patch upstream Alexander Kanavin
2024-04-19 12:19 ` [PATCH 09/19] busybox: submit CVE-2022-28391 patches upstream Alexander Kanavin
2024-04-19 12:19 ` [PATCH 10/19] busybox: remove busybox-udhcpc-no_deconfig.patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 11/19] icu: add upstream submission links for fix-install-manx.patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 12/19] mpeg2dec: remove the recipe Alexander Kanavin
2024-04-21 17:49   ` [OE-core] " Khem Raj
2024-04-21 18:18     ` Alexander Kanavin
2024-04-19 12:19 ` [PATCH 13/19] apr: drop 0007-explicitly-link-libapr-against-phtread-to-make-gold-.patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 14/19] libtraceevent: submit meson.patch upstream Alexander Kanavin
2024-04-23 11:02   ` [OE-core] " Ross Burton
2024-04-19 12:19 ` [PATCH 15/19] gstreamer1.0-plugins-good: remove 0001-qt-include-ext-qt-gstqtgl.h-instead-of-gst-gl-gstglf.patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 16/19] xinput-calibrator: mark upstream as inactive in a patch Alexander Kanavin
2024-04-19 12:19 ` [PATCH 17/19] bash: mark build-tests.patch as Inappropriate Alexander Kanavin
2024-04-19 12:19 ` [PATCH 18/19] connman: make 0002-resolve-musl-does-not-implement-res_ninit.patch libc-agnostic Alexander Kanavin
2024-04-19 12:19 ` [PATCH 19/19] connman: submit 0002-resolve-musl-does-not-implement-res_ninit.patch upstream Alexander Kanavin
2024-04-23 11:03   ` [OE-core] " Ross Burton

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=30049.1717416683403790176@lists.openembedded.org \
    --to=egyszeregy@freemail.hu \
    --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