[oe-commits] [bitbake] branch master-next updated (8ed31fb -> 0cfd58b)

git at git.openembedded.org git at git.openembedded.org
Fri Feb 26 23:45:31 UTC 2016


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

  discards  8ed31fb   providers: Fix PREFERRED_VERSION lookup for '_' in PN
  discards  1eab1bd   fetch2: Skip lockfiles and donestamps for local files
  discards  fc6ec0d   fetch2/__init__.py: Error if lockfile path invalid
  discards  ea4ec39   fetch2/__init__: Fix decodeurl to better handle urls without paths
  discards  ab74a72   wget: Set localfile for directories
       new  9e9b771   fetch2/wget: Set localfile for directories
       new  e63a9bd   fetch2/__init__: Fix decodeurl to better handle urls without paths
       new  b44c6d2   fetch2/__init__.py: Error if lockfile path invalid
       new  53a7315   fetch2: Skip lockfiles and donestamps for local files
       new  0cfd58b   providers: Fix PREFERRED_VERSION lookup for '_' in PN

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   (8ed31fb)
            \
             N -- N -- N   refs/heads/master-next (0cfd58b)

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 5 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:
 lib/bb/fetch2/__init__.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

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


More information about the Openembedded-commits mailing list