This is an automated email from the ASF dual-hosted git repository.
yuchanns pushed a change to branch feat-c-binding-writer
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard f4a29485d1 fix(bindings/c): use BlockWriter instead of StdWriter
discard 59582c79af fix(bindings/go): fix tests
discard 3847232a15 ci(bindings/go): test against service-fs
discard 2875f6715d feat(bindings/go): add writer operation
discard 32358935ff feat(bindings/c): add writer operation
add 726f9ebd20 feat(bindings/c): add writer operation
add de4eea4f1e feat(bindings/go): add writer operation
add 8ffe978767 ci(bindings/go): test against service-fs
add 8635a793d4 fix(bindings/go): fix tests
add 1ab7ae1d8f fix(bindings/c): use BlockWriter instead of StdWriter
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 (f4a29485d1)
\
N -- N -- N refs/heads/feat-c-binding-writer (1ab7ae1d8f)
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:
core/src/types/blocking_write/std_writer.rs | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
