[flang-commits] [flang] [Premerge] Premerge ci test with only change in flang (PR #130960)

[Michael Kruse via flang-commits]

https://github.com/Meinersbur created https://github.com/llvm/llvm-project/pull/130960

Test how the pre-merge CI behaves with a modification in flang: https://github.com/llvm/llvm-project/pull/128678#issuecomment-2715712219

Test whether a change in flang/ triggers building flang in Windows even though intended to be disabled.

>From 88f3148a5e2b30246eadef7a1cbcd6309c9c1361 Mon Sep 17 00:00:00 2001
From: Michael Kruse <llvm-project at meinersbur.de>
Date: Wed, 12 Mar 2025 14:20:53 +0100
Subject: [PATCH] Premerge ci test with only change in flang

---
 flang/docs/F202X.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/flang/docs/F202X.md b/flang/docs/F202X.md
index c6b5c5926efcc..67ea7fd97449a 100644
--- a/flang/docs/F202X.md
+++ b/flang/docs/F202X.md
@@ -291,7 +291,7 @@ functions whose implementations have very low priority: `SPLIT` and `TOKENIZE`.
 and could and should have been implemented once in some Fortran utility
 library for those who need a slow tokenization facility rather than
 requiring implementations in each vendor's runtime support library with
-all the extra cost and compatibilty risk that entails.
+all the extra cost and compatibility risk that entails.
 
 `SPLIT` is worse -- not only could it, like `TOKENIZE`,
 have been supplied by a Fortran utility library rather than being