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/datafusion-python.git


 discard 871b6ff  Publish built docs triggered by 
32d69752e4fb2399265b4a75c058bda63da099a7
     new 9a590de  Publish built docs triggered by 
ec835abb4da5e34556a08f72cf30a27ddeadbc95

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   (871b6ff)
            \
             N -- N -- N   refs/heads/asf-staging (9a590de)

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:
 generated/datafusion.functions.functions.html      |  4 +-
 searchindex.js                                     |  2 +-
 user-guide/common-operations/aggregations.html     | 18 ++++-----
 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          |  2 +-
 8 files changed, 50 insertions(+), 50 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to