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 483bc8de04 deploy: 5036ca803e2dfe0deb34eec4115f1d09b094dc39
     new de009f9fe8 deploy: a4bcd6d34f0d824aacfcbd2ec4cac88cce37c99f

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   (483bc8de04)
            \
             N -- N -- N   refs/heads/asf-site (de009f9fe8)

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:
 help.html     | 2 +-
 settings.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Reply via email to