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 47f2724f2e deploy: 9a5d9e99248aad3cf1f5f104b27d0f9db9e7bea6
new 3427e39384 deploy: 92dabfa95349f1b8bf008e4ca1ee182226044667
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 (47f2724f2e)
\
N -- N -- N refs/heads/asf-site (3427e39384)
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:
search.index/path/{5ea1278245.js => 0e051279a0.js} | 2 +-
search.index/path/25d0cc4a72.js | 1 +
search.index/path/ae27d510be.js | 1 -
search.index/root.js | 2 +-
4 files changed, 3 insertions(+), 3 deletions(-)
rename search.index/path/{5ea1278245.js => 0e051279a0.js} (88%)
create mode 100644 search.index/path/25d0cc4a72.js
delete mode 100644 search.index/path/ae27d510be.js
