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

driazati pushed a change to branch driazati/test_lint_split
in repository https://gitbox.apache.org/repos/asf/tvm.git


 discard 91b6b6e924 [ci] Split lint into steps
     new 58aa95af10 [ci] Split lint into steps

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   (91b6b6e924)
            \
             N -- N -- N   refs/heads/driazati/test_lint_split (58aa95af10)

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 1 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:
 Jenkinsfile               | 22 +++++++++++-----------
 ci/jenkins/Lint.groovy.j2 | 20 ++++++++++----------
 2 files changed, 21 insertions(+), 21 deletions(-)

Reply via email to