This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/junction-provenance
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard efba62977 tests/sources/source_provenance_attributes.py: Test junction
provenance
discard 06497df23 Defer source provenance check until the project is fully
loaded
discard 08e0d0f53 _stream.py: Ensure all projects are fully loaded
new d07808b2f Defer source provenance check until the project is fully
loaded
new 4d47d482c _stream.py: Ensure all projects are fully loaded
new 8e99604eb tests/sources/source_provenance_attributes.py: Test junction
provenance
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 (efba62977)
\
N -- N -- N refs/heads/jbilleter/junction-provenance (8e99604eb)
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 3 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:
src/buildstream/_project.py | 10 +++++-----
src/buildstream/element.py | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
