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.
discard 232e413 plugins/sources/git.py: Removing git source
discard c633eea tests/cachekey: Removing git source from cache key tests
discard c2814e2 tests/conftest.py: Remove git from generic source tests
discard afa4405 _testing/_utils/junction.py: Use tar for generating junctions
in source tests
add 79e9929 _testing/_utils/junction.py: Use tar for generating junctions
in source tests
add fbec4cc tests/conftest.py: Remove git from generic source tests
add 1a1439f tests/cachekey: Removing git source from cache key tests
add d3e6b5b 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 (232e413)
\
N -- N -- N refs/heads/tristan/remove-plugins (d3e6b5b)
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/_testing/_utils/junction.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)