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 f2bf4e3e02 deploy: 062ce4356d2b404295cf47dc5023a5f22179c7ad
new c30fa30285 deploy: dbd24cc95d85aa4c14f4719dd3140d723c715517
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 (f2bf4e3e02)
\
N -- N -- N refs/heads/asf-site (c30fa30285)
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:
.../buffer/boolean/struct.BooleanBuffer.html | 2 +-
arrow_buffer/buffer/null/index.html | 2 +-
arrow_buffer/buffer/null/struct.NullBuffer.html | 42 +-
arrow_buffer/buffer/struct.BooleanBuffer.html | 2 +-
arrow_buffer/buffer/struct.NullBuffer.html | 42 +-
.../entry/{e4b1dce56e.js => ec629bdb38.js} | 2 +-
search.index/path/{a5a22afe80.js => 44120d9c6b.js} | 2 +-
search.index/root.js | 2 +-
src/arrow_buffer/buffer/null.rs.html | 696 +++++++++++----------
9 files changed, 411 insertions(+), 381 deletions(-)
rename search.index/entry/{e4b1dce56e.js => ec629bdb38.js} (99%)
rename search.index/path/{a5a22afe80.js => 44120d9c6b.js} (99%)
