Hi JB, On 8/10/22 10:59, JeongBong Seo wrote:
Thanks! I resent it after the master rebase.
If there was a need to rebase (i.e. a git conflict when applying the patch on top of latest master), you need to say it's a new version in the patchset, this is usually done by passing -v 2 to git format-patch. If there was no need for it, a ping on the original mail or a patch with the [RESEND] tag would have worked too.
How can I request to merge this patch to the dunfell branch?
Once **merged** in our master branch, you can request the patch to be backported to older still-maintained branches (i.e. dunfell and kirkstone) by sending a patch with [dunfell] tag before the [PATCH] tag. Your patch needs to fit our backporting criteria (bug or security fix usually). This is appreciated by maintainers though not always necessary: they usually follow what's going into master and sometimes backport interesting patches without requests. Better send a patch if you really want/need a patch to be backported though, it helps them :).
Cheers, Quentin
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#169189): https://lists.openembedded.org/g/openembedded-core/message/169189 Mute This Topic: https://lists.openembedded.org/mt/92886214/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
