This is an automated email from the ASF dual-hosted git repository.
junouyang pushed a change to branch feat/merge_range_read
in repository https://gitbox.apache.org/repos/asf/incubator-opendal.git
discard a8d17b3bf feat: fix code
discard a7240030e feat: fix code
discard 7b40648f2 feat: remove operator rangge_read and range_reader API
add 2934405ac chore(ci): offload healthcheck logic to docker-compose
config (#2901)
add 10d60bfeb feat: remove operator rangge_read and range_reader API
add 779610e0e feat: fix code
add f1e4ea363 feat: fix code
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 (a8d17b3bf)
\
N -- N -- N refs/heads/feat/merge_range_read (f1e4ea363)
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:
.github/workflows/service_test_s3.yml | 5 -----
core/src/services/s3/fixtures/docker-compose-minio.yml | 5 +++++
2 files changed, 5 insertions(+), 5 deletions(-)
