[oe-commits] [bitbake] branch master-next updated (6fbcb1c -> 68d2e8a)

[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 bitbake.

 discard 6fbcb1c  bitbake: layerindex: allow clones to be shallow
 discard e595612  bitbake: fetch2: svn: care for path_spec
 discard db6dc22  bitbake/lib/bb/event.py: Remove duplicated ones from close matches
 discard 65419e3  cooker: Reset loghandler
 discard 9c6eb97  data: Don't allow renameVar calls with equivalent keys
 discard 0771b3a  fetch2: Allow ${AUTOREV} to be used when BB_SRCREV_POLICY is "cache"
 discard 35cf83c  fetch2: Make fetcher_compare_revisions() work
 discard 01ff109  knotty: Make the bb.command.CommandExit event terminate bitbake
 discard dc7d32f  runqueue: Possible tid handling optimisation
     add 40520d2  knotty: Make the bb.command.CommandExit event terminate bitbake
     add ffd663a  fetch2: Make fetcher_compare_revisions() work
     add ba093a3  fetch2: Allow ${AUTOREV} to be used when BB_SRCREV_POLICY is "cache"
     add 01bf091  data: Don't allow renameVar calls with equivalent keys
     add 7af80cd  cooker: Reset loghandler
     add 5612192  event: Remove duplicated items from close matches
     add 7522364  fetch2: svn: care for path_spec
     add a0c8b27  layerindex: allow clones to be shallow
     new 68d2e8a  runqueue: Possible tid handling optimisation

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   (6fbcb1c)
            \
             N -- N -- N   refs/heads/master-next (68d2e8a)

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 1 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.