[oe-commits] [openembedded-core] branch master-next updated (3fdabcd -> cb7929f)

git at git.openembedded.org git at git.openembedded.org
Tue Nov 5 12:33:44 UTC 2019


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 3fdabcd  HACK: Enable saving of packages
 discard 10cec10  oeqa: reproducible: Add option to capture bad packages
 discard 03885ca  selftest/signing: Use seperate layer test dir?
     new 6e08237  oeqa: reproducible: Add option to capture bad packages
     new b1aaafc  HACK: Enable saving of packages
     new b96e6f4  staging: Handle files moving between dependencies
     new 5350e88  sstate: Add ability to hide summary output for sstate
     new cb7929f  selftest/signing: Fix test_locked_signatures to use a temporary layer

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   (3fdabcd)
            \
             N -- N -- N   refs/heads/master-next (cb7929f)

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 5 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/sstate.bbclass    | 23 ++++++++++++-----------
 meta/classes/staging.bbclass   | 16 +++++++++++++++-
 meta/lib/oeqa/selftest/case.py |  1 -
 3 files changed, 27 insertions(+), 13 deletions(-)

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


More information about the Openembedded-commits mailing list