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

vitalii pushed a change to branch DRILL-7930
in repository https://gitbox.apache.org/repos/asf/drill.git.


 discard 1b3410e  -DdirectMemoryMb=2500 -DmemoryMb=1500
 discard 3103ffb  -DdirectMemoryMb=2500 -DmemoryMb=1500
 discard 82eda45  -DdirectMemoryMb=3000 -DmemoryMb=2000
 discard e7343d9  -DdirectMemoryMb=3000 -DmemoryMb=2000
 discard eddfbba  -DdirectMemoryMb=2500 -DmemoryMb=1500
 discard d1ce4da  -DdirectMemoryMb=3000 -DmemoryMb=1500
 discard de89a99  The same
 discard 33d79a8  -DdirectMemoryMb=3500 -DmemoryMb=1500
 discard a32cd92  -DdirectMemoryMb=4000 -DmemoryMb=1500
 discard d9140ef  -DdirectMemoryMb=4200 -DmemoryMb=1500
 discard f0cce50  DRILL-7930: Fix GitHub actions
     add 618a19a  DRILL-7930: Fix GitHub actions

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   (1b3410e)
            \
             N -- N -- N   refs/heads/DRILL-7930 (618a19a)

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:

Reply via email to