This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/pylint-2.14.5
in repository https://gitbox.apache.org/repos/asf/libcloud.git
discard 051c77b41 Bump pylint from 2.13.8 to 2.14.5
add e4b33ce72 Bump sphinx from 4.5.0 to 5.0.2
add 90cdcc13c Test formatting change.
add 054662c0e Merge branch 'trunk' of github.com:kami/libcloud into trunk
add 8df33acad Try fixing minio integration tests - it looks like new
version of the container prints different text on startup / ready.
add ef5b0d652 Fix lint.
add 346dae96a Revert "Test formatting change."
add 81a4dc06c Merge pull request #1726 from Kami/fix_integration_tests
add 2612d5cd5 Merge branch 'trunk' into dependabot/pip/sphinx-5.0.2
add 3f268e909 Merge pull request #1722 from
apache/dependabot/pip/sphinx-5.0.2
add 6f1500f7f Bump pylint from 2.13.8 to 2.14.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 (051c77b41)
\
N -- N -- N refs/heads/dependabot/pip/pylint-2.14.5 (6f1500f7f)
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:
integration/storage/test_minio.py | 5 ++++-
requirements-rtd.txt | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
