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

numinnex pushed a change to branch fix_cleanup_issues_nextnext
in repository https://gitbox.apache.org/repos/asf/iggy.git


 discard 78b7599a7 refactor(server): consensus restore, fail-stop, linear 
cleanup batch
 discard a9613bc56 refactor(consensus): single restore constructor + 
wedge/replay/ack fixes
     add dc6d34c52 refactor(consensus): single restore constructor + 
wedge/replay/ack fixes
     new b7c64210a refactor(server): consensus restore, fail-stop, linear 
cleanup batch

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   (78b7599a7)
            \
             N -- N -- N   refs/heads/fix_cleanup_issues_nextnext (b7c64210a)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

Reply via email to