This is an automated email from the ASF dual-hosted git repository.
jiayuliu pushed a change to branch datafusion-expr-window-ops
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git.
omit c0a9f56 include window frames and operator into datafusion-expr
omit 8170b2e format
omit b53e5a1 add datafusion-expr module
omit 640d7e2 move column, dfschema, etc. to common module
omit 0a93a2c move dfschema and column
add c63950d Update datafusion-common/README.md
add 9d9a31b Update datafusion/Cargo.toml
add 1b09497 include publishing
add 3d26ac4 move dfschema and column
add 839b45c move column, dfschema, etc. to common module
add c655499 add datafusion-expr module
add 6d4b3d5 format
add a52f1d7 update and add version
add 1cddd63 include window frames and operator into datafusion-expr
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 (c0a9f56)
\
N -- N -- N refs/heads/datafusion-expr-window-ops (1cddd63)
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.
No new revisions were added by this update.
Summary of changes:
datafusion-common/Cargo.toml | 3 +--
datafusion-common/README.md | 4 +++-
datafusion-expr/Cargo.toml | 3 +--
CODE_OF_CONDUCT.md => datafusion-expr/README.md | 6 +++---
datafusion/Cargo.toml | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
copy CODE_OF_CONDUCT.md => datafusion-expr/README.md (84%)
