[oe-commits] [bitbake] branch master-next updated (d817b4a -> 88fddbe)

git at git.openembedded.org git at git.openembedded.org
Wed Mar 2 22:42:14 UTC 2016


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

  discards  d817b4a   toaster: cleanup of bin/toaster startup code
  discards  da40df0   ui: remove the puccho ui
  discards  a6b8064   hob: removal of hob ui and associated ui files
  discards  a821773   fetch2/npm: Add missing ParameterError import
  discards  d3d0392   npm: in cases where shrinkwrap resolved a git URL, ignore it and grab dist.tarball
  discards  2082433   fetch2: Fix unpack for absolute file urls
  discards  571b4bb   bb/fetch2: fixes copying of file://dir; subdir=foo, bug 6128 and bug 6129
      adds  e659a3b   fetch2: fixes copying of file://dir; subdir=foo, bug 6128 and bug 6129
      adds  b8113a1   fetch2: Fix unpack for absolute file urls
      adds  eb53b92   npm: in cases where shrinkwrap resolved a git URL, ignore it and grab dist.tarball
      adds  b583a40   fetch2/npm: Add missing ParameterError import
      adds  be2ccee   hob: removal of hob ui and associated ui files
      adds  9fad1d1   ui: remove the puccho ui
      adds  88fddbe   toaster: cleanup of bin/toaster startup code

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   (d817b4a)
            \
             N -- N -- N   refs/heads/master-next (88fddbe)

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.

No new revisions were added by this update.

Summary of changes:

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


More information about the Openembedded-commits mailing list