This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/update-fixes
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 78159cf19 pytest: Set `testpaths` to fix test collection
discard 5604360cb _testing/runcli.py: Use `_yaml.roundtrip_dump()` to work
with new ruamel
discard 5d917f306 pluginoriginpip.py: Fix error type for setuptools 70
new 4ef82cdba pluginoriginpip.py: Fix error type for setuptools 70
new 8df8873e8 _testing/runcli.py: Use `_yaml.roundtrip_dump()` to work
with new ruamel
new 52b7212ac pytest: Set `testpaths` to fix test collection
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 (78159cf19)
\
N -- N -- N refs/heads/juerg/update-fixes (52b7212ac)
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:
setup.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
