This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch site
in repository https://gitbox.apache.org/repos/asf/calcite.git
discard 9047837b62 [CALCITE-6103] Use eclipse-temurin image to build and
publish javadocs for the website
discard ea0a4f28f7 [CALCITE-6047] Add news item and update date for 1.36.0
release
add 4699f02616 [CALCITE-6047] Add news item and update date for 1.36.0
release
add 8234c37b0e Prepare for next development iteration
add ae6bfa20f9 [CALCITE-6103] Use eclipse-temurin image to build and
publish javadocs for the website
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 (9047837b62)
\
N -- N -- N refs/heads/site (ae6bfa20f9)
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:
gradle.properties | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
