[oe-commits] [openembedded-core] branch sumo-next updated (b5e96ee -> 94a3ca8)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a change to branch sumo-next
in repository openembedded-core.

 discard b5e96ee  oe-build-perf-report/gitarchive: Move common useful functions to library
 discard bb9e27f  scripts/oe-git-archive: Separate out functionality to library function
 discard 94ad428  oe-build-perf-report: Fix missing buildstats comparisions
 discard a8c002c  oe-build-perf-report: Improve branch comparision handling
 discard af3cfb3  oe-build-perf-report: Allow commits from different branches
 discard 8a9ac9f  oe-build-perf-report: Allow branch without hostname
 discard 9155d04  resulttool/manualexecution: To output right test case id
 discard c16da19  resulttool/report: Enable roll-up report for a commit
 discard 659ff5c  scripts/resulttool: Enable manual result store and regression
 discard 5017222  resulttool/regression: Ensure regressoin results are sorted
 discard 3685c4c  resulttool/store: Fix missing variable causing testresult corruption
 discard 814293f   resulttool/report: Ensure ptest results are sorted
 discard 5e396b1  resulttool/report: Ensure test suites with no results show up on the report
 discard 0aa11c0  resulttool/report: Handle missing metadata sections more cleanly
 discard 7c5d14d  resulttool/store: Handle results files for multiple revisions
 discard e469b51  resulttool/resultutils: Avoids tracebacks for missing logs
 discard f565970  resulttool: Improvements to allow integration to the autobuilder
 discard 72ad469  scripts/resulttool: enable manual execution and result creation
 discard aaf8151  resulttool: enable merge, store, report and regression analysis
     add d0555e8  busybox: backport fix for issues introduced by CVE-2011-5325.patch
     add fe7c33c  coreutils: 8.29: fix native build
     add 9d8b398  lttng-ust: update to 2.10.3
     add 9666e9f  lttng-modules: update to 2.10.9
     add 4af5a79  lttng-tools: update to 2.9.11
     new bb0bc63  resulttool: enable merge, store, report and regression analysis
     new cd2ef26  scripts/resulttool: enable manual execution and result creation
     new e419556  resulttool: Improvements to allow integration to the autobuilder
     new d5d62b3  resulttool/resultutils: Avoids tracebacks for missing logs
     new 22a5982  resulttool/store: Handle results files for multiple revisions
     new 829754c  resulttool/report: Handle missing metadata sections more cleanly
     new a61ad19  resulttool/report: Ensure test suites with no results show up on the report
     new f182217   resulttool/report: Ensure ptest results are sorted
     new 811d2be  resulttool/store: Fix missing variable causing testresult corruption
     new de222c3  resulttool/regression: Ensure regressoin results are sorted
     new 514a916  scripts/resulttool: Enable manual result store and regression
     new 8f23018  resulttool/report: Enable roll-up report for a commit
     new d1dee26  resulttool/manualexecution: To output right test case id
     new e95277e  oe-build-perf-report: Allow branch without hostname
     new c635155  oe-build-perf-report: Allow commits from different branches
     new d6645c4  oe-build-perf-report: Improve branch comparision handling
     new e8651b2  oe-build-perf-report: Fix missing buildstats comparisions
     new ab5d49b  scripts/oe-git-archive: Separate out functionality to library function
     new 94a3ca8  oe-build-perf-report/gitarchive: Move common useful functions to library

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (b5e96ee)
            \
             N -- N -- N   refs/heads/sumo-next (94a3ca8)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 19 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../busybox/busybox/CVE-2011-5325-fix.patch        | 393 +++++++++++++++++++++
 meta/recipes-core/busybox/busybox_1.27.2.bb        |   1 +
 ...ush-adjust-to-glibc-2.28-libio.h-removal.patch} | 140 ++++++--
 ...ush-be-more-paranoid-about-libio.h-change.patch | 187 ++++++++++
 meta/recipes-core/coreutils/coreutils_8.29.bb      |   2 +
 ...g-modules_2.10.6.bb => lttng-modules_2.10.9.bb} |   4 +-
 ...{lttng-tools_2.9.5.bb => lttng-tools_2.9.11.bb} |   4 +-
 .../{lttng-ust_2.10.1.bb => lttng-ust_2.10.3.bb}   |   4 +-
 8 files changed, 691 insertions(+), 44 deletions(-)
 create mode 100644 meta/recipes-core/busybox/busybox/CVE-2011-5325-fix.patch
 copy meta/{recipes-devtools/m4/m4/m4-1.4.18-glibc-change-work-around.patch => recipes-core/coreutils/coreutils/0001-fflush-adjust-to-glibc-2.28-libio.h-removal.patch} (50%)
 create mode 100644 meta/recipes-core/coreutils/coreutils/0002-fflush-be-more-paranoid-about-libio.h-change.patch
 rename meta/recipes-kernel/lttng/{lttng-modules_2.10.6.bb => lttng-modules_2.10.9.bb} (90%)
 rename meta/recipes-kernel/lttng/{lttng-tools_2.9.5.bb => lttng-tools_2.9.11.bb} (97%)
 rename meta/recipes-kernel/lttng/{lttng-ust_2.10.1.bb => lttng-ust_2.10.3.bb} (90%)

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.