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

hgruszecki pushed a change to branch stm-response
in repository https://gitbox.apache.org/repos/asf/iggy.git


    omit a30175551 Merge branch 'master' into stm-response
    omit 4b9fe76d2 Merge branch 'master' into stm-response
    omit 5e8bbc8ef Merge branch 'master' into stm-response
    omit a4e849e39 Merge branch 'master' into stm-response
    omit 5cb2ffb96 feat(metadata): thread STM response into consensus Reply body
     add d0239732f dfeat(metadata): thread STM response into consensus Reply 
body

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   (a30175551)
            \
             N -- N -- N   refs/heads/stm-response (d0239732f)

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/shard/src/router.rs | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

Reply via email to