This is an automated email from the ASF dual-hosted git repository.
meteorgan pushed a change to branch rfc-read_returns_metadata
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard fae740429 roll back the changes made to the read operations
discard 4a3ffe92d add metadata() method to impl Reader
discard 7bb5b6930 fix cargo fmt
discard 8a00c722d fix pr number and issue number
discard 0df5df7d0 RFC: Read Returns Metadata
add 8c72db973 feat(bindings/c): add opendal_operator_check (#5851)
add e73dcb574 RFC: Read Returns Metadata
add 41ce44c77 fix pr number and issue number
add 4122004f1 fix cargo fmt
add 12ada0fd3 add metadata() method to impl Reader
add d9b98600d roll back the changes made to the read operations
add d2bfabc73 polish
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 (fae740429)
\
N -- N -- N refs/heads/rfc-read_returns_metadata (d2bfabc73)
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:
bindings/c/include/opendal.h | 2 ++
bindings/c/src/operator.rs | 9 +++++++++
bindings/c/tests/bdd.cpp | 5 ++++-
core/src/docs/rfcs/5871_read_returns_metadata.md | 4 ++--
core/src/types/operator/blocking_operator.rs | 24 ++++++++++++++++++++++++
5 files changed, 41 insertions(+), 3 deletions(-)
