[buildstream] branch tristan/release-cleanups updated (55574da58 -> e06880623)

[tv...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tvb pushed a change to branch tristan/release-cleanups
in repository https://gitbox.apache.org/repos/asf/buildstream.git


    omit 55574da58 doc/source/conf.py: Updating copyright year & attribute to ASF
    omit dcab38f10 LICENSE / NOTICE: Updating LICENSE and NOTICE to be compliant with apache policy
    omit 68d165189 MANIFEST.in: Ensure that LICENSE and NOTICE are included in source distribution
    omit e15a0072d Cleanup license headers for initial apache release.
     add 6d16e3a74 Cleanup license headers for initial apache release.
     add ea8b42044 MANIFEST.in: Ensure that LICENSE and NOTICE are included in source distribution
     add 8c21037ed LICENSE / NOTICE: Updating LICENSE and NOTICE to be compliant with apache policy
     add ca62392ec doc/source/conf.py: Updating copyright year & attribute to ASF
     add e06880623 COMMITTERS.rst: Adding Sander to the committer list

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   (55574da58)
            \
             N -- N -- N   refs/heads/tristan/release-cleanups (e06880623)

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.

No new revisions were added by this update.

Summary of changes:
 COMMITTERS.rst             |  3 +++
 src/buildstream/_types.pyi | 13 +++++++++++++
 2 files changed, 16 insertions(+)