This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/python-3.13
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 0ea972f2d ci: Run tests also on Fedora 41
discard 857845156 Add support for Python 3.13
discard bc8cb2a12 Update dependencies for Python 3.13 support
discard ba3ba1b50 _testing/runcli.py: Drop workaround for AIX
discard 616c283c2 Fix type errors reported by the latest version of mypy
add 57abe691b Fix type errors reported by the latest version of mypy
add 412de92d1 _testing/runcli.py: Drop workaround for AIX
add a46d66adc Update dependencies for Python 3.13 support
add 5795c2ebe Add support for Python 3.13
add 8c4008fa2 ci: Run tests also on Fedora 41
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 (0ea972f2d)
\
N -- N -- N refs/heads/juerg/python-3.13 (8c4008fa2)
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/plugin.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
