This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/sboms
in repository https://gitbox.apache.org/repos/asf/buildstream-plugins.git
discard 506f000 project.conf: Update min-version to 2.5
discard 08e2d05 tests/sources/pip_build.py: Test pip's collect_source_info()
implementation
discard cdc89a4 tests/sources/bzr.py: Test bzr's collect_source_info()
implementation
discard addf8d7 tests/sources/docker.py: Test docker's collect_source_info()
implementation
discard 108fcc8 tests/sources/git.py: Testing git's collect_source_info()
implementation
add 0559b37 tests/sources/git.py: Testing git's collect_source_info()
implementation
add 8d44a48 tests/sources/docker.py: Test docker's collect_source_info()
implementation
add 1797734 tests/sources/bzr.py: Test bzr's collect_source_info()
implementation
add 37a7c70 tests/sources/pip_build.py: Test pip's collect_source_info()
implementation
add 472e3fc project.conf: Update min-version to 2.5
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 (506f000)
\
N -- N -- N refs/heads/tristan/sboms (472e3fc)
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:
tests/sources/git.py | 1 +
1 file changed, 1 insertion(+)
