This is an automated email from the ASF dual-hosted git repository.
healchow pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-inlong.git
omit 8de3d9914 [INLONG-4598][Manager] Fix the Pulsar topic not match error
(#4599)
omit be7d72cf2 [INLONG-4591][Sort] Set the default Hive version and upgrade
the log4j to log4j2 (#4592)
omit 4906ef3a3 [INLONG-4567][Release] Update changes log for the 1.2.0
version (#4593)
new 63f105656 [INLONG-4567][Release] Update changes log for the 1.2.0
version (#4593)
new 0c1312ec9 [INLONG-4591][Sort] Set the default Hive version and upgrade
the log4j to log4j2 (#4592)
new 963e7ea7a [INLONG-4598][Manager] Fix the Pulsar topic not match error
(#4599)
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 (8de3d9914)
\
N -- N -- N refs/heads/master (963e7ea7a)
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:
CHANGES.md | 1 +
1 file changed, 1 insertion(+)
