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 1c0d771c Publish built docs triggered by 
1a6260fc74644c641b2737f0842f800157c68ddc
     new 1af7c816 Publish built docs triggered by 
f94794122f2d98797245ce6d9a3a441ef458f3af

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   (1c0d771c)
            \
             N -- N -- N   refs/heads/asf-staging (1af7c816)

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 | 36 ++++++++++----------
 user-guide/common-operations/basic-info.html   | 46 +++++++++++++-------------
 user-guide/common-operations/functions.html    | 20 +++++------
 4 files changed, 52 insertions(+), 52 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org

Reply via email to