This is an automated email from the ASF dual-hosted git repository.
meteorgan pushed a change to branch gcs_write_metadata
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard 17606bf31 remove CompleteMultipartUploadResult
discard e6663266e add CompleteMultipartUploadResult
discard 1b67eddc1 feat(services/gcs): implement write returns metadata
add 12a076cfc ci: Disable zigbuild to workaround undefined symbol (#5936)
add 9976c88d1 refactor: Remove dead code ConcurrentFutures (#5939)
add 9523fd397 feat(services/gcs): implement write returns metadata
add cc7f11a67 add CompleteMultipartUploadResult
add be29939ba remove CompleteMultipartUploadResult
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 (17606bf31)
\
N -- N -- N refs/heads/gcs_write_metadata (be29939ba)
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/release_java.yml | 6 +-
core/src/raw/futures_util.rs | 244 -------------------------------------
core/src/raw/mod.rs | 1 -
3 files changed, 5 insertions(+), 246 deletions(-)
