[oe-commits] [openembedded-core] branch master-next updated (ec94ff5 -> e8911ff)

[git at git.openembedded.org]

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

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

 discard ec94ff5  nspr: Move to meta-oe
 discard 4184b6b  nss: Move to meta-oe
 discard bef44fc  files/toolchain-shar-extract.sh: Rework PATH cleaning
 discard aa81bbd  runqemu: support multiple NICs
     new 02106d0  files/toolchain-shar-extract.sh: Rework PATH cleaning
     new d054028  nss: Move to meta-oe
     new 91c6429  nspr: Move to meta-oe
     new d218666  testsdk: Add dependency of xz-native for eSDK testing
     new 16d3943  glibc: Explicitly disable msgfmt
     new e8911ff  reproducibile_build: Fix SDE file generation when unpack reruns

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   (ec94ff5)
            \
             N -- N -- N   refs/heads/master-next (e8911ff)

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 6 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:
 meta/classes/reproducible_build.bbclass | 9 +++++----
 meta/classes/testsdk.bbclass            | 1 +
 meta/recipes-core/glibc/glibc.inc       | 3 +++
 scripts/runqemu                         | 2 +-
 4 files changed, 10 insertions(+), 5 deletions(-)

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