This is an automated email from the ASF dual-hosted git repository.
sunnianjun pushed a change to branch 5.4.1-release
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
discard 272f27a7841 Upgrade dependencies versions (#28740)
discard 3360f63f422 Update h2 license (#28739)
new dd3f91a31b9 Update h2 version (#28736)
new 04b4538cd48 Update h2 license (#28739)
new 73e063d6fa1 Upgrade dependencies versions (#28740)
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 (272f27a7841)
\
N -- N -- N refs/heads/5.4.1-release (73e063d6fa1)
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 3 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:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
