This is an automated email from the ASF dual-hosted git repository.
jark pushed a change to branch ci-rename-to-apache
in repository https://gitbox.apache.org/repos/asf/fluss.git
discard 15df98387 fix
discard 558079eae fix
discard 89a426d78 WIP
discard b6c2eca8f spotless
discard efd24eea5 WIP
discard 0e800b0db WIP
discard 0ded1f501 WIP
discard 78b503c15 WIP
discard 2ed024954 WIP
discard 0a821866c [Improve] Update NOTICE.
discard aa10e43c1 [Improve] The META-INF/services minor improvement
discard 25d34e49c [INFRA] The project package name updated to org.apache.fluss.
new db12388ec [infra] Update project package name to org.apache.fluss
new 7244a5c0d [infra] Update groupId and spotless for org.apache.fluss
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 (15df98387)
\
N -- N -- N refs/heads/ci-rename-to-apache (7244a5c0d)
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 2 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:
.../java/org/apache/fluss/lake/lance/tiering/LanceLakeCommitter.java | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
