This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/ci
in repository https://gitbox.apache.org/repos/asf/buildstream-plugins.git
discard 474edc8 Sync Python support and CI images with BuildStream
discard ba598bd testutils/python_repo.py: Make mock repo compatible with PEP
625
omit 7ea4caa git.py: Add tagger to annotated tag
omit 787aece pytest: Set `testpaths` to fix test collection
add 32e4978 git.py: Add tagger to annotated tag
add 5bd508d Merge pull request #73 from apache/juerg/git-tagger
add d42df1b pytest: Set `testpaths` to fix test collection
add 8293dec testutils/python_repo.py: Make mock repo compatible with PEP
625
add 7bde897 Sync Python support and CI images with BuildStream
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 (474edc8)
\
N -- N -- N refs/heads/juerg/ci (7bde897)
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:
