[oe-commits] [openembedded-core] branch master-next updated (eeca3a1 -> ac45d6d)

[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 eeca3a1  uninative: Switch from bz2 to xz
 discard 24f5739  yocto-uninative: Update to 2.5 release
 discard b0cb192  elfutils: fix ptest failures
 discard 1fd87d3  strace: Tweak ptest disk space management
     new a10e625  elfutils: fix ptest failures
     new 0555ede  yocto-uninative: Update to 2.5 release
     new 594b14e  uninative: Switch from bz2 to xz
     new cc0ba93  strace: Tweak ptest disk space management
     new e53ad0a  ptest-packagelists: Add mdadm
     new 4f1f744  util-linux: Fix ptest dependencies
     new ac45d6d  mdadm: Add missing ptest dependency

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

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 7 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/conf/distro/include/ptest-packagelists.inc | 1 +
 meta/recipes-core/util-linux/util-linux.inc     | 4 ++--
 meta/recipes-extended/mdadm/mdadm_4.1.bb        | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

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