This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/cargo/master/clap-4
in repository https://gitbox.apache.org/repos/asf/arrow-ballista.git
discard 75089b10 Update clap requirement from 3 to 4
add 7ae7d6a9 change flightsql.md (#476)
add 61d51d3b remove benchmark results (#478)
add 4453bafb [Minor] Bump DataFusion (#480)
add beaff216 Update clap requirement from 3 to 4
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 (75089b10)
\
N -- N -- N refs/heads/dependabot/cargo/master/clap-4 (beaff216)
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:
ballista-cli/Cargo.toml | 4 ++--
ballista/client/Cargo.toml | 4 ++--
ballista/core/Cargo.toml | 4 ++--
ballista/core/proto/datafusion.proto | 1 +
ballista/core/src/serde/physical_plan/mod.rs | 1 +
ballista/executor/Cargo.toml | 4 ++--
ballista/scheduler/Cargo.toml | 4 ++--
benchmarks/Cargo.toml | 4 ++--
docs/developer/images/ballista-benchmarks.png | Bin 24749 -> 0 bytes
docs/source/user-guide/flightsql.md | 3 ++-
examples/Cargo.toml | 2 +-
python/Cargo.toml | 2 +-
12 files changed, 18 insertions(+), 15 deletions(-)
delete mode 100644 docs/developer/images/ballista-benchmarks.png
