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
discard f19c055b6 doc/source/conf.py: Updating copyright year & attribute to
ASF
discard 2e6efa4e7 LICENSE / NOTICE: Updating LICENSE and NOTICE to be
compliant with apache policy
discard c90d5175c MANIFEST.in: Ensure that LICENSE and NOTICE are included in
source distribution
discard c141ed0e4 Cleanup license headers for initial apache release.
add e15a0072d Cleanup license headers for initial apache release.
add 68d165189 MANIFEST.in: Ensure that LICENSE and NOTICE are included in
source distribution
add a1b71ac4e LICENSE / NOTICE: Updating LICENSE and NOTICE to be
compliant with apache policy
add 2f009c1f3 doc/source/conf.py: Updating copyright year & attribute to
ASF
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 (f19c055b6)
\
N -- N -- N refs/heads/tristan/release-cleanups (2f009c1f3)
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:
src/buildstream/_protos/buildstream/v2/artifact.proto | 1 -
src/buildstream/_protos/buildstream/v2/source.proto | 1 -
2 files changed, 2 deletions(-)
