[oe-commits] [bitbake] branch master-next updated (e01bded -> fd9893c)

[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 e01bded  gitsm: Allow relative URIs when fetching
 discard 1e92b7d  fetch2/gitsm: checkout submodules recursively
 discard d9adc4f  fetch2/gitsm: handle submodules nested inside subdirs
 discard c26686e  toaster: custom image enable layer add, protect pre-cloned layers
 discard ab24e0f  toaster: disable git remote check to allow for firewalls
 discard 0337664  toaster: add 'thud' release to Toaster
 discard cbd44e0  toaster: error logs missing for cli builds
 discard 146b87b  fetch2/gitsm: fix a typo
 discard fdaca0f  fetch2/git: use correct check to decide if the shallow tarball should be unpacked
 discard 27244dd  fetch2/git: prevent access to non-existing fullshallow tarball
 discard 3709391  fetch2/git: improve readability of method need_update
     add f2d4326  bitbake-user-manual: Added new section on multiconfig builds
     add 836f994  bitbake-user-manual: Added BBMULTICONFIG support
     add fa42212  bitbake-user-manual: Added section on multicong dependencies
     new 9038e02  fetch2/git: improve readability of method need_update
     new b7f00a8  fetch2/git: prevent access to non-existing fullshallow tarball
     new 086eddc  fetch2/git: use correct check to decide if the shallow tarball should be unpacked
     new 90a3181  fetch2/gitsm: fix a typo
     new 6458cc4  toaster: error logs missing for cli builds
     new 97be301  toaster: add 'thud' release to Toaster
     new abccd40  toaster: disable git remote check to allow for firewalls
     new b310031  toaster: custom image enable layer add, protect pre-cloned layers
     new 3dbc84e  fetch2/gitsm: handle submodules nested inside subdirs
     new 377ed94  fetch2/gitsm: checkout submodules recursively
     new fd9893c  gitsm: Allow relative URIs when fetching

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   (e01bded)
            \
             N -- N -- N   refs/heads/master-next (fd9893c)

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 11 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-intro.xml                  | 157 +++++++++++++++++++++
 .../bitbake-user-manual-ref-variables.xml          |  39 +++++
 .../figures/bb_multiconfig_files.png               | Bin 0 -> 19991 bytes
 3 files changed, 196 insertions(+)
 create mode 100644 doc/bitbake-user-manual/figures/bb_multiconfig_files.png

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