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

kszucs pushed a change to branch release-7.0.0
in repository https://gitbox.apache.org/repos/asf/arrow.git.


 discard e9a7aed  ARROW-15392: [JS] Disable flaky javascript unittest
 discard 9c5f9a1  Revert "ARROW-12735: [C++] Write GDB plugin"
     add a2fe504  Revert "ARROW-12735: [C++] Write GDB plugin"
     add f1729a5  ARROW-15392: [JS] Disable flaky javascript unittest

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   (e9a7aed)
            \
             N -- N -- N   refs/heads/release-7.0.0 (f1729a5)

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:
 python/pyarrow/_engine.pyx                   | 41 --------------------
 python/pyarrow/engine.py                     |  0
 python/pyarrow/includes/libarrow_compute.pxd | 56 ----------------------------
 python/pyarrow/includes/libarrow_engine.pxd  | 37 ------------------
 4 files changed, 134 deletions(-)
 delete mode 100644 python/pyarrow/_engine.pyx
 delete mode 100644 python/pyarrow/engine.py
 delete mode 100644 python/pyarrow/includes/libarrow_compute.pxd
 delete mode 100644 python/pyarrow/includes/libarrow_engine.pxd

Reply via email to