[oe-commits] [bitbake] branch master-next updated (7d5868a -> 07b6054)

[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 7d5868a  bb: siggen: Print more info when basehash are mis-matched
 discard 4493786  bb: siggen: Make dump_sigfile and compare_sigfiles print uuid4
 discard 15067e4  bitbake-diffsigs: Use 4 spaces as indent for recursecb
 discard ed49e58  toaster: update to Warrior
     add 5a69795  bitbake-user-manual: Added section on modifying variables
     new 7dbcab1  toaster: update to Warrior
     new 5127a8d  bitbake-diffsigs: Use 4 spaces as indent for recursecb
     new 724b4a5  bb: siggen: Make dump_sigfile and compare_sigfiles print uuid4
     new 07b6054  bb: siggen: Print more info when basehash are mis-matched

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   (7d5868a)
            \
             N -- N -- N   refs/heads/master-next (07b6054)

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 4 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:
 .../bitbake-user-manual-metadata.xml               | 72 ++++++++++++++++++++++
 1 file changed, 72 insertions(+)

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