This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/78/29378/3
in repository toolchain/jenkins-scripts.
discards 878935435 tcwg_kernel-build.sh: Add --mode continue
adds cfab8ab16 tcwg_kernel-build.sh: Add --mode continue
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 (878935435)
\
N -- N -- N refs/changes/78/29378/3 (cfab8ab16)
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/78/29378/2
in repository toolchain/jenkins-scripts.
discards 033d16fb3 tcwg_kernel-build.sh: Add --mode continue
adds 139c302c9 tcwg_kernel-build.sh: Add --mode continue
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 (033d16fb3)
\
N -- N -- N refs/changes/78/29378/2 (139c302c9)
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/78/29378/1
in repository toolchain/jenkins-scripts.
discards 1b96a8b85 tcwg_kernel-build.sh: Add --mode continue
adds b2fef1ab7 tcwg_kernel-build.sh: Add --mode continue
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 (1b96a8b85)
\
N -- N -- N refs/changes/78/29378/1 (b2fef1ab7)
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/77/47277/1
in repository toolchain/jenkins-scripts.
discards b5e0dfba4 ci-autotest.sh,tcwg_chromium-*.sh: Automatically choose ci demo mode
adds 9540f2574 ci-autotest.sh,tcwg_chromium-*.sh: Automatically choose ci demo mode
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 (b5e0dfba4)
\
N -- N -- N refs/changes/77/47277/1 (9540f2574)
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/77/47177/2
in repository toolchain/jenkins-scripts.
discards 7b24543f6 tcwg_chromium-build.sh: Skip git fetch when useless
adds cbe03f510 tcwg_chromium-build.sh: Skip git fetch when useless
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 (7b24543f6)
\
N -- N -- N refs/changes/77/47177/2 (cbe03f510)
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/77/47177/1
in repository toolchain/jenkins-scripts.
discards 4b01548c4 tcwg_chromium-build.sh: Skip git fetch when useless
adds f37494d29 tcwg_chromium-build.sh: Skip git fetch when useless
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 (4b01548c4)
\
N -- N -- N refs/changes/77/47177/1 (f37494d29)
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/77/46977/3
in repository toolchain/jenkins-scripts.
discards 8f1e392b0 lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
adds 978107e47 lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
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 (8f1e392b0)
\
N -- N -- N refs/changes/77/46977/3 (978107e47)
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/77/46977/2
in repository toolchain/jenkins-scripts.
discards 9812906a8 lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
new e16b1134b lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
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 (9812906a8)
\
N -- N -- N refs/changes/77/46977/2 (e16b1134b)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
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/77/46977/1
in repository toolchain/jenkins-scripts.
discards 1c7d5f4b9 lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
new da491c6de lnt-utils.sh,round-robin-notify.sh: Add all variability infos [...]
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 (1c7d5f4b9)
\
N -- N -- N refs/changes/77/46977/1 (da491c6de)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
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/77/46677/2
in repository toolchain/jenkins-scripts.
discards f1819e1c2 tcwg-lnt/create-server.sh: create db with stable-url feature enabled
adds d29147362 tcwg-lnt/create-server.sh: create db with stable-url feature enabled
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 (f1819e1c2)
\
N -- N -- N refs/changes/77/46677/2 (d29147362)
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.