[oe-commits] [openembedded-core] branch master-next updated (76fb9f9 -> e618fbb)

[git at git.openembedded.org]

rpurdie pushed a change to branch master-next
in repository openembedded-core.

  discards  76fb9f9   Revert "base.bbclass wipe ${S} before unpacking source"
  discards  1d98800   base.bbclass wipe ${S} before unpacking source
  discards  9da3084   build summary: add TCMODE to build summary
  discards  bd16892   build summary: add gcc version being used.
      adds  da7a2c7   useradd-staticids: use map() instead of imap()
       new  ac90e72   build summary: add gcc version being used.
       new  93e697a   build summary: add TCMODE to build summary
       new  7d37821   base.bbclass wipe ${S} before unpacking source
       new  e618fbb   Revert "base.bbclass wipe ${S} before unpacking source"

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   (76fb9f9)
            \
             N -- N -- N   refs/heads/master-next (e618fbb)

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 "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 meta/classes/useradd-staticids.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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