Paul Gortmaker 2102b8c9b6 file: update SRCREV for 5.30 to fix fetch fail on missing commit ...

Machines that cloned a while ago will have the commit, but new
deployments won't because it seems the upstream changed/rebased
and the old commit ID has been garbage-collected away.  Hence
the fetch fails to check out the named commit ID.

Both the old (gone) commit, and the "new" commit show the same
dates and commit log and point at 5.30, so hopefully this is
the right thing to do.  A git diff of the two seems to only show
a blanket uprev of CVS tags and deletion of a couple autogen'd
files, and no real source changes.

Cc: Christos Zoulas <christos@zoulas.com>
(From OE-Core rev: adb71e06768adadda7b69c3b5e81ca3ad67237f4)

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2017-03-17 16:53:05 +00:00

..

file

file: 5.27 -> 5.28

2016-07-12 23:10:15 +01:00

file_5.30.bb

file: update SRCREV for 5.30 to fix fetch fail on missing commit

2017-03-17 16:53:05 +00:00