This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/remove-plugins
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
omit d3e6b5b plugins/sources/git.py: Removing git source
omit 1a1439f tests/cachekey: Removing git source from cache key tests
omit fbec4cc tests/conftest.py: Remove git from generic source tests
omit 79e9929 _testing/_utils/junction.py: Use tar for generating junctions
in source tests
new feed690 _testing/_utils/junction.py: Use tar for generating junctions
in source tests
new 4f0f9f1 tests/conftest.py: Remove git from generic source tests
new e79bf03 tests/cachekey: Removing git source from cache key tests
new d22f854 plugins/sources/git.py: Removing git source
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 (d3e6b5b)
\
N -- N -- N refs/heads/tristan/remove-plugins (d22f854)
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:
src/buildstream/_testing/_utils/junction.py | 1 +
1 file changed, 1 insertion(+)
