This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/38089/1
in repository toolchain/jenkins-scripts.
discards 0f89dc5c1 tcwg-update-llvmbot-containers.sh: Remove aarch64 libcxx buildbot
adds 466c1dcee tcwg-update-llvmbot-containers.sh: Remove aarch64 libcxx buildbot
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (0f89dc5c1)
\
N -- N -- N refs/changes/89/38089/1 (466c1dcee)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/34089/1
in repository toolchain/jenkins-scripts.
discards cd12daec2 abe-bisect.sh: Require GOOTGIT and BADGIT instead of GOOD and BAD
adds 876d0ade0 abe-bisect.sh: Require GOOTGIT and BADGIT instead of GOOD and BAD
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (cd12daec2)
\
N -- N -- N refs/changes/89/34089/1 (876d0ade0)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/32989/4
in repository toolchain/jenkins-scripts.
discards 91a1271c8 tcwg_bmk-build.sh: Fix code-size comparison
adds 8d766da49 tcwg_bmk-build.sh: Fix code-size comparison
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (91a1271c8)
\
N -- N -- N refs/changes/89/32989/4 (8d766da49)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/32989/3
in repository toolchain/jenkins-scripts.
discards a8010a567 tcwg_bmk-build.sh: Fix code-size comparison
adds 42ef78f40 tcwg_bmk-build.sh: Fix code-size comparison
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (a8010a567)
\
N -- N -- N refs/changes/89/32989/3 (42ef78f40)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/32989/2
in repository toolchain/jenkins-scripts.
discards 4ff8d921a tcwg_bmk-build.sh: Fix code-size comparison
adds 91885e43f tcwg_bmk-build.sh: Fix code-size comparison
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (4ff8d921a)
\
N -- N -- N refs/changes/89/32989/2 (91885e43f)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/32989/1
in repository toolchain/jenkins-scripts.
discards 234e44aa7 tcwg_bmk-build.sh: Fix code-size comparison
adds cfc41cd02 tcwg_bmk-build.sh: Fix code-size comparison
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (234e44aa7)
\
N -- N -- N refs/changes/89/32989/1 (cfc41cd02)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/30489/3
in repository toolchain/jenkins-scripts.
discards f64d30e3f tcwg_kernel-bisect.sh: Fix linux-next rebase workaround for g [...]
discards 56317f8c7 tcwg_kernel-bisect.sh: Handle bisecting between branches/tags
adds 0f4f485b6 tcwg_kernel-bisect.sh: Handle bisecting between branches/tags
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (f64d30e3f)
\
N -- N -- N refs/changes/89/30489/3 (0f4f485b6)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 383 --------------------------------------------------
1 file changed, 383 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/30489/2
in repository toolchain/jenkins-scripts.
discards 122941b7d tcwg_kernel-bisect.sh: Fix linux-next rebase workaround for g [...]
discards 4b1c0db36 tcwg_kernel-bisect.sh: Handle bisecting between branches/tags
adds 5a0537376 tcwg_kernel-bisect.sh: Handle bisecting between branches/tags
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (122941b7d)
\
N -- N -- N refs/changes/89/30489/2 (5a0537376)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 383 --------------------------------------------------
1 file changed, 383 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/30489/1
in repository toolchain/jenkins-scripts.
discards 059e4803d tcwg_kernel-bisect.sh: Fix linux-next rebase workaround for g [...]
discards fb7005c40 tcwg_kernel-bisect.sh: Handle bisecting between branches/tags
discards 644c2eba2 tcwg-dev-build: Enable builds using manifests
adds 8f89d0a47 tcwg-dev-build: Enable builds using manifests
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (059e4803d)
\
N -- N -- N refs/changes/89/30489/1 (8f89d0a47)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 383 --------------------------------------------------
1 file changed, 383 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/89/29489/3
in repository toolchain/jenkins-scripts.
discards c0db51589 jenkins-helpers.sh: Add git_rev_parse_long
adds 4897c9262 jenkins-helpers.sh: Add git_rev_parse_long
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (c0db51589)
\
N -- N -- N refs/changes/89/29489/3 (4897c9262)
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.