stop mentioning the old selfhosted arm64 runner setup (git-for-window…

…s#5630)

We don't use the selfhosted runners anymore, drop the outdated paragraph
describing that old setup.

monitor-components: skip curl prereleases (git-for-windows#5629)

curl recently started releasing rc versions, but we don't want to act on
them, so there is no need to open issues about every rc version.

Fix t0060.221 on Windows/ARM64 (git-for-windows#5610)

Apparently my tests of git-for-windows#5586
had been incomplete. This here patch is needed to let t0060.221 pass
(where it verifies that `git.exe` sets `MSYSTEM` correctly if that
environment variable has not yet been set): Simply reverse the order of
the tests whether to set `MINGW64` or `CLANGARM64` to avoid using the
former on Windows/ARM64 by mistake.

Upgrade to mimalloc v2.2.3 (git-for-windows#5508)

Git for Windows still carries [mimalloc
v2.1.2](https://github.com/microsoft/mimalloc/releases/tag/v2.1.2),
which is almost 2 years old. Let's upgrade.

clangarm64: let the tests pass! (git-for-windows#5586)

I encountered these issues that had hitherto escaped us [when I worked
on letting the `ci-artifacts` workflow in git-sdk-arm64 also build Git
and run the test
suite](git-for-windows/git-sdk-arm64#37) by way
of validating the `minimal-sdk` artifact.

Mind, this PR does not only adjust a test case that was previously too
fixated on x86_64. There are two real issues that this PR addresses and
that were found via the test suite:

- When the environment variable `MSYSTEM` is not yet set, it now is set
appropriately even on Windows/ARM64 (and the `PATH` is adjusted
accordingly).
- The tree traversal limit designed to avoid stack overflows needed to
be adjusted for the clangarm64 builds.

Fix CI builds again (git-for-windows#5590)

I noticed that the CI builds of `shears/main` were failing, as well as
the PR builds of git-for-windows#5586. The reasons are outside of Git for Windows, but
the fixes need to be inside anyway.

fixup! mingw: support long paths (git-for-windows#5550)

When rebasing c8b6c1d (mingw: support long paths, 2015-07-28) on
top of 391bcea (compat/mingw: support POSIX semantics for atomic
renames, 2024-10-27) a newly introduced MAX_PATH buffer was not
increased to MAX_LONG_PATH.

This fixes git-for-windows#5476

mingw_rename: support ReFS on Windows 2022 (git-for-windows#5515)

Git on Windows 2022 fails to write config files on ReFS with the error
message "Function not implemented". The reason is that
`ERROR_NOT_SUPPORTED` is reported (not `ERROR_INVALID_PARAMETER`, as
expected). Let's handle both errors the same: by falling back to the
best-effort option, namely to rename without POSIX semantics.

This fixes git-for-windows#5427

Replace the superseded wiki URLs (git-for-windows#5495)

This is a follow-up for
git-for-windows/git-for-windows.github.io#59.

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>