You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by xu...@apache.org on 2026/09/22 07:24:18 UTC

(opendal-yinyang) branch xuanwo/file-runtime updated (a320349 -> da33637)

This is an automated email from the ASF dual-hosted git repository.

Xuanwo pushed a change to branch xuanwo/file-runtime
in repository https://gitbox.apache.org/repos/asf/opendal-yinyang.git


 discard a320349  fix: preserve staging write order across cancellation
 discard 666de4f  feat: add recoverable managed file handles
 discard c0586d3  test: retry bounded service writer contention
 discard 8a3cc0f  feat: add durable metadata service publication
    omit d42372e  refactor: separate logical transactions from object publication
     add 027e1b7  refactor: separate logical transactions from object publication (#49)
     add 4c1ea4d  feat: add durable metadata service publication
     add 4e86679  test: retry bounded service writer contention
     add 947009f  feat: add recoverable managed file handles
     add da33637  fix: preserve staging write order across cancellation

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   (a320349)
            \
             N -- N -- N   refs/heads/xuanwo/file-runtime (da33637)

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: