- Absolutely right
- Unfortunately I was totally in PR mode and accidentally pushed to the
repository master. Have now glued me in a few notes on the screen. (sorry
for the poor commit on the master)
Jan Kiszka schrieb am Donnerstag, 3. März 2022 um 14:41:07 UTC+1:
> You miss your signed-off, and I would recommend leaving a few words on
> they "why", in this case on what the impact was/is.
>
> On 03.03.22 13:24, Michael Haener wrote:
> > ---
> > recipes-bsp/efibootguard/efibootguard_0.10.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/recipes-bsp/efibootguard/efibootguard_0.10.bb
> b/recipes-bsp/efibootguard/efibootguard_0.10.bb
> > index 8a50b77..f25a67e 100644
> > --- a/recipes-bsp/efibootguard/efibootguard_0.10.bb
> > +++ b/recipes-bsp/efibootguard/efibootguard_0.10.bb
> > @@ -12,7 +12,7 @@
> > LICENSE = "GPLv2"
> > LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> >
> > -SRC_URI = "git://
> github.com/siemens/efibootguard.git;protocol=https;branch=master"
> > +SRC_URI = "gitsm://
> github.com/siemens/efibootguard.git;protocol=https;branch=master"
> > SRCREV = "99435e3d7ac960883c951db151ff3ac3c4088458"
> >
> > S = "${WORKDIR}/git"
>
> In addition: Please prefix meta-efibootguard patches with
> "[meta-efibootguard][PATCH ..." to help quickly identifying which repo
> is targeted. Maybe worth documenting in a contribution guide of the
> layer when keeping the mail-based workflow.
>
> Jan
>
> --
> Siemens AG, Technology
> 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 view this discussion on the web visit
https://groups.google.com/d/msgid/efibootguard-dev/e5d19560-e3ac-4447-8577-6ffda276c460n%40googlegroups.com.
