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-erlang.git


 discard e1d42ba  deploy: ad4cba77800a9b98b1f824205dc35f20aa3592e7
     new 08210e0  deploy: 49e8e777cc531f180169d3c116a91d9c0617e9cb

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   (e1d42ba)
            \
             N -- N -- N   refs/heads/asf-site (08210e0)

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:
 main/arrow.epub             | Bin 54406 -> 54411 bytes
 main/arrow_ipc_message.html |   2 +-
 main/quick-run-through.html | 100 ++++++++++++++++++++++----------------------
 main/readme.html            |   2 +-
 4 files changed, 52 insertions(+), 52 deletions(-)

Reply via email to