This is an automated email from the git hooks/post-receive script.
"Diana Picus pushed a change to branch diana/release/11.0.0%wip in repository toolchain/jenkins-scripts.
omits c5ce29e1 Increase memory allocation for build containers omits 95b2210d tcwg-llvm-release: Deal with flang and mlir new 369a4485 tcwg-llvm-release: Deal with flang and mlir new fa498a6d Increase memory allocation for build containers
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (c5ce29e1) \ N -- N -- N refs/heads/diana/release/11.0.0%wip (fa498a6d)
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 2 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: tcwg-llvm-release.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)