This is an automated email from the ASF dual-hosted git repository.

areusch pushed a change to branch areusch/freeze-dependencies
in repository https://gitbox.apache.org/repos/asf/tvm.git


 discard d7ee612f7c Fix all scripts which reference python3 in the docker 
containers.
 discard ba2e4a14cd try to fix hashes
 discard b0f9181fe5 test Jenkins infra
 discard 08c7341d9e Adjust package installs with py-deps to use the virtualenv.
 discard b81b8a2ec4 Align Python and package install process in all containers.
 discard d47c86e928 Add docker container for freezing python deps.
     new 0353e8608a Add docker container for freezing python deps.
     new 5b9513da9f Align Python and package install process in all containers.
     new 18d2ae0fdb Adjust package installs with py-deps to use the virtualenv.
     new 0357389cad test Jenkins infra
     new 5dceac2c0f try to fix hashes
     new f3fa6b8474 Fix all scripts which reference python3 in the docker 
containers.

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   (d7ee612f7c)
            \
             N -- N -- N   refs/heads/areusch/freeze-dependencies (f3fa6b8474)

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 6 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/install/ubuntu1804_install_python.sh | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

Reply via email to