This is an automated email from the ASF dual-hosted git repository.
francischuang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/calcite-avatica-go.git.
discard a8df670 [CALCITE-3033] Move release process to separate HOWTO
document to be consistent with how the avatica docs are structured
discard 8cbd923 [CALCITE-3032] Simplify docker-compose.yml for running tests
and development mode, change release process to use a docker container to build
in a clean environment and include automation for uploading and promoting
releases
new 4ae034e [CALCITE-3032] Simplify docker-compose.yml for running tests
and development mode, change release process to use a docker container to build
in a clean environment and include automation for uploading and promoting
releases
new 1a57b05 [CALCITE-3033] Move release process to separate HOWTO
document to be consistent with how the avatica docs are structured
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 (a8df670)
\
N -- N -- N refs/heads/master (1a57b05)
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 173 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:
docker.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
