This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/97/45597/2
in repository toolchain/jenkins-scripts.
discards ade6e2020 tcwg_bmk-build.sh: Make transitional workaround for annex mor [...]
adds a948dfd9d tcwg_bmk-build.sh: Make transitional workaround for annex mor [...]
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 (ade6e2020)
\
N -- N -- N refs/changes/97/45597/2 (a948dfd9d)
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/97/45597/1
in repository toolchain/jenkins-scripts.
discards 0abae3f74 tcwg_bmk-build.sh: Make transitional workaround for annex mor [...]
adds f9058b89b tcwg_bmk-build.sh: Make transitional workaround for annex mor [...]
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 (0abae3f74)
\
N -- N -- N refs/changes/97/45597/1 (f9058b89b)
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/97/44497/4
in repository toolchain/jenkins-scripts.
discards 838c1318a round-robin-rewrite.sh: New script to re-write base-artifacts
adds c1147a6a4 round-robin-rewrite.sh: New script to re-write base-artifacts
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 (838c1318a)
\
N -- N -- N refs/changes/97/44497/4 (c1147a6a4)
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/97/44497/3
in repository toolchain/jenkins-scripts.
discards bc58cb8d2 round-robin-rewrite.sh: New script to re-write base-artifacts
adds ccf8f195a round-robin-rewrite.sh: New script to re-write base-artifacts
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 (bc58cb8d2)
\
N -- N -- N refs/changes/97/44497/3 (ccf8f195a)
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/97/44497/2
in repository toolchain/jenkins-scripts.
discards 0abbaaee3 round-robin-rewrite.sh: New script to re-write base-artifacts
new 12de36d6b round-robin-rewrite.sh: New script to re-write base-artifacts
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 (0abbaaee3)
\
N -- N -- N refs/changes/97/44497/2 (12de36d6b)
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/97/44497/1
in repository toolchain/jenkins-scripts.
discards 995c71d1d round-robin-rewrite.sh: New script to re-write base-artifacts
new bb91e68bd round-robin-rewrite.sh: New script to re-write base-artifacts
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 (995c71d1d)
\
N -- N -- N refs/changes/97/44497/1 (bb91e68bd)
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/97/44297/1
in repository toolchain/jenkins-scripts.
discards 83cb599a3 round-robin.sh (build_abe): Remove workaround for GDB testsuite
adds 929b33218 round-robin.sh (build_abe): Remove workaround for GDB testsuite
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 (83cb599a3)
\
N -- N -- N refs/changes/97/44297/1 (929b33218)
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/97/43697/2
in repository toolchain/jenkins-scripts.
discards 343887f3c tcwg_{aosp,bmk}-build.sh: Use get_git_history() to fetch "fir [...]
adds a01535e07 tcwg_{aosp,bmk}-build.sh: Use get_git_history() to fetch "fir [...]
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 (343887f3c)
\
N -- N -- N refs/changes/97/43697/2 (a01535e07)
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/97/43697/1
in repository toolchain/jenkins-scripts.
discards c5ff258d9 tcwg_{aosp,bmk}-build.sh: Use get_git_history() to fetch "fir [...]
new 016ba58c7 tcwg_{aosp,bmk}-build.sh: Use get_git_history() to fetch "fir [...]
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 (c5ff258d9)
\
N -- N -- N refs/changes/97/43697/1 (016ba58c7)
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/97/43597/2
in repository toolchain/jenkins-scripts.
discards fd1b18607 generate-cimonitor-dashboard.py: improve diag
adds bc56aeba9 generate-cimonitor-dashboard.py: improve diag
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 (fd1b18607)
\
N -- N -- N refs/changes/97/43597/2 (bc56aeba9)
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.