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 e39528d91e deploy: 191aa7c97da3d69c3fa235f4bf6849b03a74194d
     new 5b4616e8ab deploy: 9c6065c451a1131393191ea828151639f031bf87

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   (e39528d91e)
            \
             N -- N -- N   refs/heads/asf-site (5b4616e8ab)

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/3649b9484f4d.js                      | 1 +
 search.index/entry/865275deec8d.js                      | 1 -
 search.index/entry/{87f6d2aa8fe2.js => f0e8ac1169e0.js} | 2 +-
 search.index/path/198d2298ce60.js                       | 1 -
 search.index/path/367d885f00f2.js                       | 1 +
 search.index/root.js                                    | 2 +-
 6 files changed, 4 insertions(+), 4 deletions(-)
 create mode 100644 search.index/entry/3649b9484f4d.js
 delete mode 100644 search.index/entry/865275deec8d.js
 rename search.index/entry/{87f6d2aa8fe2.js => f0e8ac1169e0.js} (85%)
 delete mode 100644 search.index/path/198d2298ce60.js
 create mode 100644 search.index/path/367d885f00f2.js

Reply via email to