[oe-commits] [meta-openembedded] branch master-next updated (ba0e770 -> af6adb7)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

khem pushed a change to branch master-next
in repository meta-openembedded.

 discard ba0e770  python3-django: fix UPSTREAM_CHECK_REGEX
 discard a6c2f4b  pkcs11-helper: add UPSTREAM_CHECK_GITTAGREGEX
 discard 78a38cb  abseil-cpp: set PV in the recipe
 discard 1228d2c  babeld: add UPSTREAM_CHECK_GITTAGREGEX
 discard 4a23729  exfat-utils: fix upstream version check
 discard 8317488  layer.conf: add meta-python to LAYERDEPENDS
     new 9966a72  exfat-utils: fix upstream version check
     new 42ac9f5  babeld: add UPSTREAM_CHECK_GITTAGREGEX
     new 0d68b0c  abseil-cpp: set PV in the recipe
     new 46d3d41  pkcs11-helper: add UPSTREAM_CHECK_GITTAGREGEX
     new af6adb7  python3-django: fix UPSTREAM_CHECK_REGEX

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

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-oe/conf/layer.conf | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

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