Re: [yocto-patches] [yocto-autobuilder-helper][PATCH] send_qa_email: add git-describe output if possible

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Tue, Jan 27, 2026 at 10:40:10AM +0100, Yoann Congal wrote:
> Le lun. 26 janv. 2026 � 15:19, Yoann Congal <yoann.congal@smile.fr> a
> �crit :
> 
> >
> >
> > Le lun. 26 janv. 2026 � 10:25, Mikko Rapeli <mikko.rapeli@linaro.org> a
> > �crit :
> >
> >> Hi,
> >>
> >> On Mon, Jan 26, 2026 at 09:52:53AM +0100, Yoann Congal via
> >> lists.yoctoproject.org wrote:
> >> > From: Yoann Congal <yoann.congal@smile.fr>
> >> >
> >> > This would allow to quickly identify commits that are not on the right
> >> > branch.
> >> >
> >> > Partial example of output on my whinlatter-nut branch:
> >> >   bitbake: 74f8a927ca6a20342072e5579182aea917b6dc30
> >> (yocto-5.3-3-g74f8a927c)
> >> >   meta-yocto: 6973ca663aaa9c3ab517ee960ab7985a5bf54c07
> >> (yocto-5.3-1-g6973ca6)
> >> >   openembedded-core: b4e7819b99d9c1a8995eba87e6f466fd8c77e14a
> >> (yocto-5.3-73-gb4e7819b99)
> >> > (It shows that every commits are correctly after yocto-5.3)
> >>
> >> The output may or may not work, and may actually confuse users:
> >>
> >> bitbake$ git describe --match yocto-* origin/master
> >> yocto-5.3-52-gcdd79c1768ac
> >> core$ git describe --match yocto-* origin/master
> >> yocto-5.1-4541-g6c31c2a73185
> >> meta-yocto$ git describe --match yocto-* origin/master
> >> yocto-5.0.10-40-gc23c19e0b300
> >>
> >> and I don't seem to be able to find out in a few minutes which branch
> >> of bitbake is used with core and meta-yocto whinlatter branches
> >> since the branch is not called "whinlatter" but bitbake version.
> >> Oh bitbake
> >> default-registry/configurations/oe-nodistro-whinlatter.conf.json
> >> has it as "2.16" but openembedded-core doesn't seem to know which bitbake
> >> version is correct for whinlatter.
> >>
> >> I hope this works for "whinlatter" and other releases in the future
> >> but the tags are a bit messy stil.
> >>
> >
> > Yes, agreed. That works well only for stable branches after the first
> > release.
> > Maybe we can only take this patch for those branches?
> >
> 
> This is something I can check locally before greenlighting a build for QA,
> just tried it for 4.0.33-rc3.
> => We can drop this patch.

Is there any possibility to fix this for yocto 6.0, for example that yocto-6.x.y tags
would be aligned on master branches too?

Cheers,

-Mikko