This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/85/44385/4
in repository toolchain/jenkins-scripts.
discards fb49d3344 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds 6bfd6f7f5 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (fb49d3344)
\
N -- N -- N refs/changes/85/44385/4 (6bfd6f7f5)
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/85/44385/3
in repository toolchain/jenkins-scripts.
discards 8b3455736 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds a7c46902f docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (8b3455736)
\
N -- N -- N refs/changes/85/44385/3 (a7c46902f)
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/85/44385/2
in repository toolchain/jenkins-scripts.
discards 04ca4884a docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds 81180ac90 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (04ca4884a)
\
N -- N -- N refs/changes/85/44385/2 (81180ac90)
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/85/44385/12
in repository toolchain/jenkins-scripts.
discards dde788957 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds b16f8231b docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (dde788957)
\
N -- N -- N refs/changes/85/44385/12 (b16f8231b)
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/85/44385/11
in repository toolchain/jenkins-scripts.
discards 4c1c87fe6 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds f1e17fd71 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (4c1c87fe6)
\
N -- N -- N refs/changes/85/44385/11 (f1e17fd71)
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/85/44385/10
in repository toolchain/jenkins-scripts.
discards 3e3ad7160 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds 88c651b26 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (3e3ad7160)
\
N -- N -- N refs/changes/85/44385/10 (88c651b26)
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/85/44385/1
in repository toolchain/jenkins-scripts.
discards cdfdff807 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds 050874fa0 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (cdfdff807)
\
N -- N -- N refs/changes/85/44385/1 (050874fa0)
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/85/44285/1
in repository toolchain/jenkins-scripts.
discards f40a67c42 tcwg_gnu-build.sh: Fix typo
adds 2f89c4057 tcwg_gnu-build.sh: Fix typo
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 (f40a67c42)
\
N -- N -- N refs/changes/85/44285/1 (2f89c4057)
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/85/43685/3
in repository toolchain/jenkins-scripts.
discards 231bfe529 round-robin.sh (build_abe): Use ABE to construct lists of fla [...]
adds 011a0cbe9 round-robin.sh (build_abe): Use ABE to construct lists of fla [...]
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 (231bfe529)
\
N -- N -- N refs/changes/85/43685/3 (011a0cbe9)
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/85/43685/2
in repository toolchain/jenkins-scripts.
discards a0f19f745 round-robin.sh (build_abe): Use ABE to construct lists of fla [...]
adds c9ce14c37 round-robin.sh (build_abe): Use ABE to construct lists of fla [...]
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 (a0f19f745)
\
N -- N -- N refs/changes/85/43685/2 (c9ce14c37)
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.