This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion-python.git
discard 1f2504c Publish built docs triggered by
e1b37401a2d1af86ab16b899f1dda8237a0d3535
new 174e083 Publish built docs triggered by
0b22c977dbdfbfe1e0536e0b1bf79045e7bf0e7e
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 (1f2504c)
\
N -- N -- N refs/heads/asf-staging (174e083)
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:
searchindex.js | 2 +-
user-guide/common-operations/aggregations.html | 34 ++++++++--------
user-guide/common-operations/basic-info.html | 46 +++++++++++-----------
user-guide/common-operations/functions.html | 22 +++++------
user-guide/common-operations/joins.html | 4 +-
.../common-operations/select-and-filter.html | 2 +-
user-guide/common-operations/windows.html | 22 +++++------
user-guide/introduction.html | 2 +-
8 files changed, 67 insertions(+), 67 deletions(-)
