This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/13/30013/2
in repository toolchain/jenkins-scripts.
discards b24c88785 tcwg_kernel-bisect.sh: Update email configuration
discards fe8e1720f tcwg_kernel-bisect.sh: Add a few lines of build errors to the email.
discards e69a96373 tcwg_kernel-bisect.sh: Add configuration details to the email body
discards e9dc86fb7 tcwg_kernel/*: Remove unused configuration files.
adds 1edbdc4fc tcwg_kernel/*: Remove unused configuration files.
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 (b24c88785)
\
N -- N -- N refs/changes/13/30013/2 (1edbdc4fc)
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 | 363 --------------------------------------------------
1 file changed, 363 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/13/30013/1
in repository toolchain/jenkins-scripts.
discards 87e78e046 tcwg_kernel-bisect.sh: Update email configuration
discards 6d6a5066b tcwg_kernel-bisect.sh: Add a few lines of build errors to the email.
discards c7a245aa5 tcwg_kernel-bisect.sh: Add configuration details to the email body
discards e9dc86fb7 tcwg_kernel/*: Remove unused configuration files.
adds 1edbdc4fc tcwg_kernel/*: Remove unused configuration files.
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 (87e78e046)
\
N -- N -- N refs/changes/13/30013/1 (1edbdc4fc)
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 | 363 --------------------------------------------------
1 file changed, 363 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/12/46812/3
in repository toolchain/jenkins-scripts.
discards 234bb40bd precommit-ssh-apply.sh: Remove temporary directory upon exit
adds e3be1ff20 precommit-ssh-apply.sh: Remove temporary directory upon exit
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 (234bb40bd)
\
N -- N -- N refs/changes/12/46812/3 (e3be1ff20)
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/12/46812/2
in repository toolchain/jenkins-scripts.
discards d90e4d017 precommit-ssh-apply.sh: Remove temporary directory upon exit
new 61693ce76 precommit-ssh-apply.sh: Remove temporary directory upon exit
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 (d90e4d017)
\
N -- N -- N refs/changes/12/46812/2 (61693ce76)
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/12/46812/1
in repository toolchain/jenkins-scripts.
discards 8367c8616 precommit-ssh-apply.sh: Remove temporary directory upon exit
new 58ab5807b precommit-ssh-apply.sh: Remove temporary directory upon exit
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 (8367c8616)
\
N -- N -- N refs/changes/12/46812/1 (58ab5807b)
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/12/46612/1
in repository toolchain/jenkins-scripts.
discards f89b3ba69 Revert "round-robin.sh (build_abe) Enable maintainer_mode in [...]
adds b8f7a47ba Revert "round-robin.sh (build_abe) Enable maintainer_mode in [...]
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 (f89b3ba69)
\
N -- N -- N refs/changes/12/46612/1 (b8f7a47ba)
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/12/46312/2
in repository toolchain/jenkins-scripts.
discards 689359c72 round-robin.sh (build_abe): Improve revision and LAST_UPDATED [...]
adds 60ae1f3ad round-robin.sh (build_abe): Improve revision and LAST_UPDATED [...]
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 (689359c72)
\
N -- N -- N refs/changes/12/46312/2 (60ae1f3ad)
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/12/46312/1
in repository toolchain/jenkins-scripts.
discards 82ce3848a round-robin.sh (build_abe): Improve revision and LAST_UPDATED [...]
adds e36eccfe3 round-robin.sh (build_abe): Improve revision and LAST_UPDATED [...]
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 (82ce3848a)
\
N -- N -- N refs/changes/12/46312/1 (e36eccfe3)
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/12/46212/2
in repository toolchain/jenkins-scripts.
discards f7f6bc441 pw-trigger.sh: Fix thinko, which broke precommit testing for 2 weeks
adds dc194f0bf pw-trigger.sh: Fix thinko, which broke precommit testing for 2 weeks
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 (f7f6bc441)
\
N -- N -- N refs/changes/12/46212/2 (dc194f0bf)
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/12/46212/1
in repository toolchain/jenkins-scripts.
discards f678b4e13 pw-trigger.sh: Fix thinko, which broke precommit testing for 2 weeks
new e78579df6 pw-trigger.sh: Fix thinko, which broke precommit testing for 2 weeks
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 (f678b4e13)
\
N -- N -- N refs/changes/12/46212/1 (e78579df6)
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.