This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/49/31049/2
in repository toolchain/jenkins-scripts.
discards 1a938a0a0 Add support for bootstrap-lto-lean config.
adds f2bcc3b67 Add support for bootstrap-lto-lean config.
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 (1a938a0a0)
\
N -- N -- N refs/changes/49/31049/2 (f2bcc3b67)
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/49/31049/1
in repository toolchain/jenkins-scripts.
discards 4619cf0c3 Add support for bootstrap-lto-lean config.
new cb8959111 Add support for bootstrap-lto-lean config.
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 (4619cf0c3)
\
N -- N -- N refs/changes/49/31049/1 (cb8959111)
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/49/30749/4
in repository toolchain/jenkins-scripts.
discards 4f5214da5 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
adds a11ae38f0 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
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 (4f5214da5)
\
N -- N -- N refs/changes/49/30749/4 (a11ae38f0)
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/49/30749/3
in repository toolchain/jenkins-scripts.
discards 8b3672b6d Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
adds 570df1232 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
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 (8b3672b6d)
\
N -- N -- N refs/changes/49/30749/3 (570df1232)
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/49/30749/2
in repository toolchain/jenkins-scripts.
discards c946901c9 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
adds bbce7f2c9 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
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 (c946901c9)
\
N -- N -- N refs/changes/49/30749/2 (bbce7f2c9)
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/49/30749/1
in repository toolchain/jenkins-scripts.
discards 02071f84d Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
adds 1ee34f991 Patch [1/3] Merge tcwg_gnu: jenkins-helpers.sh - s/tcwg_kerne [...]
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 (02071f84d)
\
N -- N -- N refs/changes/49/30749/1 (1ee34f991)
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/49/30349/2
in repository toolchain/jenkins-scripts.
discards 7c7293dd6 convert_args_to_variables: Document "==" syntax
adds bfce8330d convert_args_to_variables: Document "==" syntax
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 (7c7293dd6)
\
N -- N -- N refs/changes/49/30349/2 (bfce8330d)
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/49/30349/1
in repository toolchain/jenkins-scripts.
discards 927f44cf8 convert_args_to_variables: Document "==" syntax
new 527d74c2f convert_args_to_variables: Document "==" syntax
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 (927f44cf8)
\
N -- N -- N refs/changes/49/30349/1 (527d74c2f)
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/49/30049/3
in repository toolchain/jenkins-scripts.
discards aaa033fb3 round-robin.sh: Add support for handling new configurations
adds 4f95c3c1f round-robin.sh: Add support for handling new configurations
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 (aaa033fb3)
\
N -- N -- N refs/changes/49/30049/3 (4f95c3c1f)
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/49/30049/2
in repository toolchain/jenkins-scripts.
discards a196372cd round-robin.sh: Add support for handling new configurations
adds 40aeed683 round-robin.sh: Add support for handling new configurations
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 (a196372cd)
\
N -- N -- N refs/changes/49/30049/2 (40aeed683)
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.