This is an automated email from the ASF dual-hosted git repository.
amashenkov pushed a change to branch ignite-20503
in repository https://gitbox.apache.org/repos/asf/ignite-3.git
discard bfcc6abb93 Minors after merge with master.
discard ebc340aa1d Minors after review.
discard 6c2a735f51 Drop ExecutionTarget.finalise method.
discard 8ca6c997be add tests
discard 981e71dee7 Minor.
discard c73c7c4cbc Minor.
discard 94788b4871 Styles.
discard 1d7f9ccbfe revert unrelated change
discard 58e1478c35 wip
discard 3317de5fa5 wip
add 6ec26881b7 wip
add 142018696e Get rid of finalise method
add a489acfd32 Minors after review.
add 189378c17d Minors after merge with master.
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 (bfcc6abb93)
\
N -- N -- N refs/heads/ignite-20503 (189378c17d)
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:
.../internal/sql/engine/exec/mapping/largecluster/AbstractTarget.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
