[oe-commits] [openembedded-core] branch master-next updated (fec9a87 -> d485e77)

[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 fec9a87  fixup
 discard b7c89cf  babeltrace2: initialize the other_entry pointer
 discard 8722f01  curl: upgrade 7.69.0 -> 7.69.1
 discard c9ff467  oeqa: enable testresults.json for testexport
 discard cb3780e  oeqa/runtime/context.py: fix typo
 discard 56c5d6f  weston-init: Allow use of weston without input devices
 discard 3f45a0f  boost: fix reproducibilty issues
 discard e896a48  dnf: fix reproducibilty issue
 discard dfe8340  gtk-doc: Fix reproducibity issues
 discard 3f6b8c5  ltp: fix reproducibilty issues
 discard bec9cf7  qemu: Fix reproducibilty issues
 discard a020e04  strace: Fix reproducibility issues
 discard 58449ec  glib-2.0: Correct multilib conflict
 discard 2d0cbb9  babletrace2: make manpages multilib identical
 discard 6f01a53  rootfs-postcommands: Remove spaces before ; in -ROOTFS_..._COMMAND
 discard 38ce012  HACK: signing: Add extra test debug
     add bf959e6  oeqa/runtime/context.py: fix typo
     add d3af3cf  curl: upgrade 7.69.0 -> 7.69.1
     new edabeb8  HACK: signing: Add extra test debug
     new 07b7e38  rootfs-postcommands: Remove spaces before ; in -ROOTFS_..._COMMAND
     new c83046a  babletrace2: make manpages multilib identical
     new 6cedaf0  glib-2.0: Correct multilib conflict
     new 96ad3231 strace: Fix reproducibility issues
     new e69a9d8  qemu: Fix reproducibilty issues
     new dde53e5  ltp: fix reproducibilty issues
     new 7270d6b  gtk-doc: Fix reproducibity issues
     new 81a181a  dnf: fix reproducibilty issue
     new c7d155d  boost: fix reproducibilty issues
     new 6d522f2  weston-init: Allow use of weston without input devices
     new da1611a  oeqa: enable testresults.json for testexport
     new 002f99c  babeltrace2: initialize the other_entry pointer
     new d485e77  fixup

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

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 14 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:

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