This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/46/41646/2 in repository toolchain/jenkins-scripts.
discards a21eb6e3f Apply downstream patch in build_llvm to emit number of vector [...] adds 55fb40c16 Apply downstream patch in build_llvm to emit number of vector [...]
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 (a21eb6e3f) \ N -- N -- N refs/changes/46/41646/2 (55fb40c16)
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: