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 b6c65851d3 deploy: 89075a75b937eb8630b2e3f7d3b7fc4b6e6aece7
     new 7f63df3543 deploy: 44b6ded1340d8f3c1bfece18e871ed3be4c394d6

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   (b6c65851d3)
            \
             N -- N -- N   refs/heads/asf-site (7f63df3543)

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:
 arrow_array/index.html      | 46 +++++++++++++++++++++-
 src/arrow_array/lib.rs.html | 96 ++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 140 insertions(+), 2 deletions(-)

Reply via email to