Skip to contentSkip to conversation

Question about merger process for patches under different branch

DISCUSSION Ashish Mishra 2 participants 2 messages Nov 11, 2025

lore
Share & tools
lore
#0 lore raw

Hi Team,

I am trying to get a better picture so that we avoid un-necessary message which interrupts the branch maintainer's Can team please confirm if I am understanding usage of below branches correct:

1) meta-openembedded-contrib
The patches which are being "considered" or "scheduled" to be tested for merge can be seen from these branches
From these patches, whichever passes the auto-build will then move to branch-next
*The presence of patches here can be considered as "patch considered for auto build and testing for respective branch "*
To know which patches are scheduled for next test , we can look at
master      : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/master ( https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/master ) scarthgap : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/scarthgap
kirkstone  : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/kirkstone

2) branch-next @ meta-openembedded
These are the patches which have been tested & will shortly be added in their respective branch *But the presence of patches here can be considered as "merged" in respective branch*

master       : https://git.openembedded.org/meta-openembedded/log/?h=master-next
scarthgap : https://git.openembedded.org/meta-openembedded/log/?h=scarthgap-next
kirkstone  : https://git.openembedded.org/meta-openembedded/log/?h=kirkstone-next

3) Any ball mark, how much time we can consider it takes for patches to be available in respective branch from "branch-next".

Thanks ,
Ashish Kumar Mishra

#1 lore raw

This probably should be asked on openembedded-devel list?

Alex

Quoted 36 lines · Ashish Mishra via lists.openembedded.org

Hi Team,

I am trying to get a better picture so that we avoid un-necessary message which interrupts the branch maintainer's Can team please confirm if I am understanding usage of below branches correct:

1) meta-openembedded-contrib
The patches which are being "considered" or "scheduled" to be tested for merge can be seen from these branches
From these patches, whichever passes the auto-build will then move to branch-next
The presence of patches here can be considered as "patch considered for auto build and testing for respective branch "
To know which patches are scheduled for next test , we can look at
master : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/master
scarthgap : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/scarthgap
kirkstone : https://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/kirkstone

2) branch-next @ meta-openembedded
These are the patches which have been tested & will shortly be added in their respective branch
But the presence of patches here can be considered as "merged" in respective branch
master : https://git.openembedded.org/meta-openembedded/log/?h=master-next
scarthgap : https://git.openembedded.org/meta-openembedded/log/?h=scarthgap-next
kirkstone : https://git.openembedded.org/meta-openembedded/log/?h=kirkstone-next

3) Any ball mark, how much time we can consider it takes for patches to be available in respective branch from "branch-next".

Thanks ,
Ashish Kumar Mishra

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#226145): https://lists.openembedded.org/g/openembedded-core/message/226145
Mute This Topic: https://lists.openembedded.org/mt/116234126/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-