public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Leitner" <richard.leitner@skidata.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] dtc: update to 1.6.0
Date: Wed, 6 May 2020 09:19:19 +0200	[thread overview]
Message-ID: <20200506071919.GC250994@pcleri> (raw)
In-Reply-To: <20200506071016.GA31672@localhost>

On Wed, May 06, 2020 at 10:10:16AM +0300, Adrian Bunk wrote:
> On Tue, May 05, 2020 at 01:55:35PM +0200, Richard Leitner wrote:
> >...
> > --- a/meta/recipes-kernel/dtc/dtc_1.5.1.bb
> > +++ b/meta/recipes-kernel/dtc/dtc_1.6.0.bb
> > @@ -3,7 +3,7 @@ require dtc.inc
> >  LIC_FILES_CHKSUM = "file://GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> >  		    file://libfdt/libfdt.h;beginline=4;endline=7;md5=05bb357cfb75cae7d2b01d2ee8d76407"
> >  
> > -SRCREV = "60e0db3d65a1218b0d5a29474e769f28a18e3ca6"
> > +SRCREV = "v${PV}"
> >...
> 
> It is tempting to use tags, but it is a bad idea.
> Upstream might move a tag to a different commit.
> Someone might do a man-in-the-middle attack on a specific user,
> and there is no other verification of the sources apart from
> the commit hash.

Thanks for the info. Is this documented somewhere?

How should I proceed on this patch as it was already applied to
master-next? Should I send a v2 or a "fix patch"?

Furthermore I'll send a v2 for my other series which is not applied yet
(https://patchwork.openembedded.org/patch/172341/).

regards;rl

> 
> cu
> Adrian

  reply	other threads:[~2020-05-06  7:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 11:55 [PATCH] dtc: update to 1.6.0 Richard Leitner
2020-05-06  7:10 ` [OE-core] " Adrian Bunk
2020-05-06  7:19   ` Richard Leitner [this message]
2020-05-06 10:18     ` Adrian Bunk
2020-05-07 20:02   ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200506071919.GC250994@pcleri \
    --to=richard.leitner@skidata.com \
    --cc=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox