summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/file/file_5.25.bb
Commit message (Collapse)AuthorAgeFilesLines
* Revert "file: update SRCREV for 5.25 to fix fetch fail on missing commit"Richard Purdie2017-03-211-1/+1
| | | | | | | | This reverts commit b35225c88ff681a4a903f7fb4612ac768214f539. Upstream restored the original hashes. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* file: update SRCREV for 5.25 to fix fetch fail on missing commitPaul Gortmaker2017-03-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | 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.25, 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. (From OE-Core rev: adb71e06768adadda7b69c3b5e81ca3ad67237f4) Cc: Christos Zoulas <christos@zoulas.com> (From OE-Core rev: b35225c88ff681a4a903f7fb4612ac768214f539) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* file: 5.24 -> 5.25Robert Yang2016-01-151-0/+47
(From OE-Core rev: 84e782e4c83236fe4a058309a9a5027589d27223) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>