[oe-commits] [openembedded-core] branch master-next updated (138bafd -> e2613ed)

git at git.openembedded.org git at git.openembedded.org
Thu Mar 9 21:48:49 UTC 2017


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 138bafd  fixup
 discard e6df45e  test without flex
 discard c342058  test without unlzma
 discard e808669  quilt: Don't add hardcoded links to utilities
 discard accbd89  libpng12: Use rm instead of unlink
 discard ca8a87b  tzcode-native: Set cc to ${CC}
 discard ba4cfd0  base/bitbake.conf: Filter contents of PATH to only allow whitelisted tools
     new 2f1e631  tzcode-native: Set cc to ${CC}
     new 22ee8b6  libpng12: Use rm instead of unlink
     new 2b13981  quilt: Don't add hardcoded links to utilities
     new e2613ed  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   (138bafd)
            \
             N -- N -- N   refs/heads/master-next (e2613ed)

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/base.bbclass | 5 +++--
 meta/conf/bitbake.conf    | 9 +++++----
 2 files changed, 8 insertions(+), 6 deletions(-)

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


More information about the Openembedded-commits mailing list