You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by rm...@apache.org on 2024/10/09 19:18:40 UTC

(hbase) branch 28897-branch-2.6 updated (9e58941cf61 -> ae08313e380)

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

rmattingly pushed a change to branch 28897-branch-2.6
in repository https://gitbox.apache.org/repos/asf/hbase.git


    omit 9e58941cf61 HBASE-28897 Force CF compatibility during incremental backup (#6340)
     add ae08313e380 HBASE-28897 Force CF compatibility during incremental backup (#6340) (#6358)

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   (9e58941cf61)
            \
             N -- N -- N   refs/heads/28897-branch-2.6 (ae08313e380)

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:
 .../java/org/apache/hadoop/hbase/backup/TestIncrementalBackup.java     | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)