On 2018-01-10 13:09, [ext] Andreas J. Reichel wrote: > From: Andreas Reichel <[email protected]> > > To really support yocto, we must introduce different branches > for used yocto versions. My suggestion is to create the > following two branches from master to apply this patch-set to: > > * rocko > * rocko-next
Do Yocto rocko and master already deviate in a relevant degree for us? > > In future there should also be: > > * krogoth, krogoth-next krogoth is seriously dead. > * morthy, morty-next morty is taking its last breaths. > * pyro, pyro-next For pyro, we probably need backports then, right? > > This way, we are compliant with other open source meta-layers and > don't run into problems when using the layer with different yocto > versions. > > That said, this patch series adds support for Yocto Rocko. > Tests for older systems are on the way. Ah, ok. Will have a look at the patches soon. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/580b9935-3ebe-02b0-e112-fc34b4e4a58e%40siemens.com. For more options, visit https://groups.google.com/d/optout.
