This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
discard 8539d21016 deploy: 560596e89a0c73878b6e1d521199b714a7dd8f49
new a56fffb4e7 deploy: 533fe4fd467e1dd09869215e848f0e247ea58274
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 (8539d21016)
\
N -- N -- N refs/heads/asf-site (a56fffb4e7)
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/entry/{981bbbbfe99e.js => 1aeb3686c721.js} | 2 +-
search.index/entry/{bff37ec31585.js => 50e58fcb6776.js} | 2 +-
search.index/path/0af24fd93783.js | 1 -
search.index/path/b9c7ca493abe.js | 1 +
search.index/root.js | 2 +-
5 files changed, 4 insertions(+), 4 deletions(-)
rename search.index/entry/{981bbbbfe99e.js => 1aeb3686c721.js} (72%)
rename search.index/entry/{bff37ec31585.js => 50e58fcb6776.js} (64%)
delete mode 100644 search.index/path/0af24fd93783.js
create mode 100644 search.index/path/b9c7ca493abe.js
