[oe-commits] [openembedded-core] branch master-next updated (e7238c6 -> 0157975)

[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 e7238c6  runqemu-gen-tapdevs: Improve help text with an example
 discard 39744a8  quilt: Avoid hardcoding paths into output
 discard dc94328  cdrtools-native: Fix when cc is missing
 discard 1a11942  base/bitbake.conf: Filter contents of PATH to only allow whitelisted tools
 discard 0545dba  quilt: Don't add hardcoded links to utilities
 discard 216eafb  libpng12: Use rm instead of unlink
 discard 0722227  tzcode-native: Set cc to ${CC}
 discard 1b3b3c0  toolchain-shar-extract.sh: Ensure sbin directories are in PATH in clean environment
 discard 3d1c8a1  core-image-sato: exclude musl and x32
 discard c9cf24c  XXX add go to sato image
 discard 448b783  go: Add recipes for golang compilers and tools
 discard 391f960  chkconfig-alternatives-native: fix obey_variables
 discard 5a08bea  classes: add gitupstream class
     add 6486dd7  chkconfig-alternatives-native: fix obey_variables
     add 8c49ab4  toolchain-shar-extract.sh: Ensure sbin directories are in PATH in clean environment
     add 402080c  tzcode-native: Set cc to ${CC}
     add d292641  libpng12: Use rm instead of unlink
     add b319e43  quilt: Don't add hardcoded links to utilities
     add a6816d6  cdrtools-native: Fix when cc is missing
     add e0188f6  quilt: Avoid hardcoding paths into output
     add 056a9da  runqemu-gen-tapdevs: Improve help text with an example
     new 78615e9  go: Add recipes for golang compilers and tools
     new c1f4d5c  XXX add go to sato image
     new 96371dc  core-image-sato: exclude musl and x32
     new 0157975  base/bitbake.conf: Filter contents of PATH to only allow whitelisted tools

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

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 4 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/gitupstream.bbclass | 25 -------------------------
 1 file changed, 25 deletions(-)
 delete mode 100644 meta/classes/gitupstream.bbclass

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