> You can replace the patch below with a backport of what was accepted

No, I can't do that because the current shadow's master and v4.19.4 (last
release) are quite different. I cannot simply cherry-pick my commit and
apply it as a patch, the only way to backport is to manually completely
recreate these changes for v4.19.4. I have already discussed this topic
with Randy ([email protected]), and he advised me that waiting
for a stable release (they are promising late June 2026) is better than
doing this complex backport.

Though, if required, I don't mind creating a different patch special for
v4.19.4 so we can use the new configure option ASAP. But since the shadow
recipe will have to be rewritten anyway after v4.20 release, should I? I
don't really know what would be better, so I appreciate any opinion.

чт, 7 мая 2026 г. в 14:18, Alexander Kanavin <[email protected]>:

> On Thu, 7 May 2026 at 12:24, frezidok1 via lists.openembedded.org
> <[email protected]> wrote:
> > After they release v4.20 we can remove the patch and rewrite recipe with
> the configure option.
>
> We don't need to wait for 4.20 to do that. You can replace the patch
> below with a backport of what was accepted, and then tweak the recipe
> to use the newly added option.
>
> > -Upstream-Status: Inappropriate [Would upstream accept a configure
> option?]
> > +Upstream-Status: Submitted [Merged to upstream's master, waiting for
> release]
>
> Also this change isn't accurate: the patch that was submitted and
> merged is not the same as this one. If this patch is kept, then the
> accurate status would be:
>
> Inappropriate [upstream has accepted a better patch at $link]
>
> Alex
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#236582): 
https://lists.openembedded.org/g/openembedded-core/message/236582
Mute This Topic: https://lists.openembedded.org/mt/119194645/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to