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

aloyszhang pushed a change to branch rebase
in repository https://gitbox.apache.org/repos/asf/inlong.git


 discard 05c04c80c9 [INLONG-9862][Manager] Support submit flink job for offline 
sync (#9865)
 discard 045e04b768 [INLONG-9822][Manager] Support flink job runtime execution 
mode configuration (#9823)
 discard ce64702219 [INLONG-9813][Manager] Support offline data sync management 
(#9814)
 discard 84511f056f [INLONG-9781][Manager] Add offline sync task type 
definition (#9787)
     new 1e0fddc0a8 [INLONG-9781][Manager] Add offline sync task type 
definition (#9787)
     new dfb22f4d8e [INLONG-9813][Manager] Support offline data sync management 
(#9814)
     new ff3c351401 [INLONG-9822][Manager] Support flink job runtime execution 
mode configuration (#9823)
     new 65d3a928ea [INLONG-9862][Manager] Support submit flink job for offline 
sync (#9865)

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   (05c04c80c9)
            \
             N -- N -- N   refs/heads/rebase (65d3a928ea)

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 4 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:
 .../main/java/org/apache/inlong/manager/plugin/flink/FlinkService.java  | 2 --
 1 file changed, 2 deletions(-)

Reply via email to