This is an automated email from the ASF dual-hosted git repository.
mchades pushed a change to branch
cherry-pick-branch-0.6-79742f364f9fccf189e6333dc5c7539c409b76dc
in repository https://gitbox.apache.org/repos/asf/gravitino.git
discard f50a4e428 [#4699] fix(server): The error response of addUser should
meet the REST specification (#4704)
add 6a175120c [#4695] Fix (python-client): Fix gradlew
:clients:client-python:build failed if the package does not contain .git
directory (#4705)
add 1a6129cac [#4699] fix(server): The error response of addUser should
meet the REST specification (#4704)
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 (f50a4e428)
\
N -- N -- N
refs/heads/cherry-pick-branch-0.6-79742f364f9fccf189e6333dc5c7539c409b76dc
(1a6129cac)
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:
clients/client-python/gravitino/constants/root.py | 1 +
clients/client-python/scripts/generate_version.py | 24 +++++++++++++++++++----
2 files changed, 21 insertions(+), 4 deletions(-)
