Skip to contentSkip to conversation

Fix for the OpenBMC 2.6 release

DISCUSSION Joseph Reynolds 2 participants 2 messages Apr 11, 2019 – Apr 12, 2019

lore
Share & tools
lore
#0 lore raw

I would like to make a fix for the OpenBMC 2.6 release (branch=thud), that is https://github.com/openbmc/openbmc/tree/thud
The fix is the OpenBMC 2.6 version of this fix: https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/20393

Is there a process to get fixes into the 2.6 release? My fix is in a meta-layer, so I follow the technical process here: https://github.com/openbmc/docs/blob/master/subtree.md. Except how do I push my change into branch=thud? (I am still a git novice.)

- Joseph

#1 lore raw
Quoted 4 lines · Joseph Reynolds

I would like to make a fix for the OpenBMC 2.6 release (branch=thud), that is https://github.com/openbmc/openbmc/tree/thud
The fix is the OpenBMC 2.6 version of this fix: https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/20393

Is there a process to get fixes into the 2.6 release? My fix is in a meta-layer, so I follow the technical process here: https://github.com/openbmc/docs/blob/master/subtree.md. Except how do I push my change into branch=thud? (I am still a git novice.)

Hi Joseph

Just push to refs/for/thud instead of refs/for/master. Make sure your local ref/branch is based on thud and not master.

-brad