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 845009de47 deploy: 2d89d277b18717260121de82f2c909be00e3fa25
new 887bd27b1f deploy: 03b652ea7a8e6d57f9e536d678a1ea2825458423
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 (845009de47)
\
N -- N -- N refs/heads/asf-site (887bd27b1f)
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/{9704b687ed.js => 31cf962515.js} | 2 +-
search.index/root.js | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename search.index/path/{9704b687ed.js => 31cf962515.js} (89%)
