This is an automated email from the ASF dual-hosted git repository.
areusch pushed a change to branch revert-13073-micro-always-on
in repository https://gitbox.apache.org/repos/asf/tvm.git
discard 79706486f9 revert USE_MICRO for wasm, unrelated
discard 0e27cc2bc3 USE_MICRO ON for minimal and wasm to work around CI
limitation.
discard 5be8107847 Revert "[microTVM] enable building microTVM components by
default (#13073)"
add 5b1a1e3d39 [skip ci][ci][wasm] Add package-lock.json to git (#13505)
add 6fa966f6be Revert "[microTVM] enable building microTVM components by
default (#13073)"
add 624efb24c6 USE_MICRO ON for minimal and wasm to work around CI
limitation.
add 3e3dd32a92 revert USE_MICRO for wasm, unrelated
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 (79706486f9)
\
N -- N -- N refs/heads/revert-13073-micro-always-on (3e3dd32a92)
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:
web/.gitignore | 1 -
web/package-lock.json | 6724 +++++++++++++++++++++++++++++++++++++++++++++++++
web/package.json | 3 +-
3 files changed, 6726 insertions(+), 2 deletions(-)
create mode 100644 web/package-lock.json
