Wed, Feb 26, 2025, 06:35:33 PM GMT

Some `clangarm64` fixes (#5439)

Most notably, this fixes
https://github.com/git-for-windows/git/issues/5431, i.e. that the ARM64
flavor of Git for Windows does not use `/etc/gitconfig` by mistake, but
`/clangarm64/etc/gitconfig` instead.

My original intention was to fix only that issue, but when I fired up a
Git for Windows/ARM64 SDK and tried to build, I immediately ran into
trouble, then noticed places where ARM64 was not yet handled, and one
thing led to another and now it's a 6-patch PR instead of a single-patch
one.

Fri, Feb 21, 2025, 12:02:13 PM GMT

compat/mingw: rename the symlink, not the target (#5437)

This fixes yet another fall-out from the `mingw_rename()` change that was introduced in v2.48.0.

Thu, Feb 6, 2025, 06:33:46 PM GMT

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

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

Thu, Feb 6, 2025, 06:12:08 PM GMT

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

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

Thu, Feb 6, 2025, 01:30:38 PM GMT

SECURITY.md: use the new Git for Windows snapshots URL (#5402)

The `SECURITY.md` document mentions Git for Windows' snapshots and
helpfully provides a link.

For almost eight years, Git for Windows' snapshots were hosted [on Azure
Blobs](https://wingit.blob.core.windows.net/files/index.html).

As of a combination of PRs
(https://github.com/git-for-windows/git-for-windows-automation/pull/109,
https://github.com/git-for-windows/gfw-helper-github-app/pull/117),
snapshots are not only now built and deployed via GitHub Actions instead
of Azure Pipelines (and ARM64 artifacts are now included, too), they are
also hosted [on
GitHub](https://github.com/git-for-windows/git-snapshots/releases/),
with the main page being hosted [on GitHub
Pages](https://github.com/git-for-windows/git-snapshots/commits/gh-pages).

Therefore, the original link now redirects to a new location (which is
also a lot easier to remember): http://gitforwindows.org/git-snapshots.
Let's adjust the link to link there directly.

This is a companion PR of
https://github.com/git-for-windows/git-for-windows-automation/pull/111
and of https://github.com/git-for-windows/build-extra/pull/589.

Thu, Jan 30, 2025, 04:19:52 PM GMT

Drop support for CI builds using Azure Pipelines (#5389)

A long time ago, we used Azure Pipelines for CI builds. Eventually, when
GitHub Actions was spawned from Azure Pipelines, we moved over to that
system for CI/PR builds.

However, I've tried to keep a working Azure Pipelines definition around
for the embargoed releases, to be able to increase confidence in the
patches by running the full CI build in a private Azure DevOps project
(we cannot do the same on GitHub because even the very generous offer of
50,000 build minutes per month is no match for Git's test suite).

It took a lot of work, and it would take even more work what with
upstream's "remove stale code for Azure Pipelines" part of
`ps/ci-misc-updates`.

Time to let it go.

Thu, Jan 23, 2025, 02:48:44 PM GMT

Apply some v2.48 regression bugfixes (#5376)

Now that most of the Git contributors are back from the holidays, there
is an influx of bug fixes. This is precisely why I held off from rushing
Git for Windows v2.48.0 out the door.

These bug fixes are mostly taken from upstream's branches; In some
cases, though, I had to apply them directly from the Git mailing list
because they did not make it into git/git yet.

I deem those bug fixes necessary to get Git for Windows into a somewhat
healthy state again.

Thu, Jan 23, 2025, 02:48:44 PM GMT

Apply some v2.48 regression bugfixes (#5376)

Now that most of the Git contributors are back from the holidays, there
is an influx of bug fixes. This is precisely why I held off from rushing
Git for Windows v2.48.0 out the door.

These bug fixes are mostly taken from upstream's branches; In some
cases, though, I had to apply them directly from the Git mailing list
because they did not make it into git/git yet.

I deem those bug fixes necessary to get Git for Windows into a somewhat
healthy state again.

Thu, Jan 23, 2025, 02:48:44 PM GMT

Apply some v2.48 regression bugfixes (#5376)

Now that most of the Git contributors are back from the holidays, there
is an influx of bug fixes. This is precisely why I held off from rushing
Git for Windows v2.48.0 out the door.

These bug fixes are mostly taken from upstream's branches; In some
cases, though, I had to apply them directly from the Git mailing list
because they did not make it into git/git yet.

I deem those bug fixes necessary to get Git for Windows into a somewhat
healthy state again.

Thu, 23 Jan 2025 15:48:44 +0100

Apply some v2.48 regression bugfixes (#5376)

Now that most of the Git contributors are back from the holidays, there
is an influx of bug fixes. This is precisely why I held off from rushing
Git for Windows v2.48.0 out the door.

These bug fixes are mostly taken from upstream's branches; In some
cases, though, I had to apply them directly from the Git mailing list
because they did not make it into git/git yet.

I deem those bug fixes necessary to get Git for Windows into a somewhat
healthy state again.