[oe-commits] [bitbake] branch master-next updated (3a28e02 -> 5be7ce7)
git at git.openembedded.org
git at git.openembedded.org
Wed Jan 22 15:57:59 UTC 2020
This is an automated email from the git hooks/post-receive script.
rpurdie pushed a change to branch master-next
in repository bitbake.
discard 3a28e02 tests/fetch: Allow wget upgrade tests to run against a local server
discard 322c029 fixup
discard 49d6a7a fix2
discard 5c0fa9d bitbake: siggen: Cache unihash values to avoid cache lookup
discard 0a0497e bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
discard e1104b5 runqueue: Possible tid handling optimisation
add d5a4a35 tests/fetch: Allow wget upgrade tests to run against a local server
new c44ab98 runqueue: Possible tid handling optimisation
new 9252a0e bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
new 711c2c4 bitbake: siggen: Cache unihash values to avoid cache lookup
new 2c289c6 fix2
new 5be7ce7 fixup
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 (3a28e02)
\
N -- N -- N refs/heads/master-next (5be7ce7)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list