This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
discard c5d628e434 deploy: aca75aeb799281a87c52059bb6bb02f845b1e292
new ddbbe5a070 deploy: 83ebd7248be4779700ab81dddd14d63c87fe5109
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 (c5d628e434)
\
N -- N -- N refs/heads/asf-site (ddbbe5a070)
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 1 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:
.../flight_service_server/trait.FlightService.html | 4 +-
.../flight_service_server/trait.FlightService.html | 4 +-
arrow_flight/sql/server/enum.DoPutError.html | 4 +-
.../sql/server/fn.arrow_error_to_status.html | 2 +-
.../sql/server/fn.decode_error_to_status.html | 2 +-
arrow_flight/sql/server/index.html | 2 +-
.../server/struct.PeekableFlightDataStream.html | 10 +-
.../sql/server/trait.FlightSqlService.html | 39 +-
.../entry/{04e7c4c859.js => f5e146994b.js} | 2 +-
search.index/path/{d8662f5889.js => 8ba642d655.js} | 2 +-
search.index/root.js | 2 +-
src/arrow_flight/sql/server.rs.html | 1048 ++++++++++----------
12 files changed, 562 insertions(+), 559 deletions(-)
rename search.index/entry/{04e7c4c859.js => f5e146994b.js} (99%)
rename search.index/path/{d8662f5889.js => 8ba642d655.js} (89%)
