Releases: git-for-windows/git-snapshots
Releases · git-for-windows/git-snapshots
Tue, Jul 15, 2025, 09:35:09 AM GMT
CONTRIBUTING.md: fix PuTTY URL (#5725) Already in c2a2fd57402e (CONTRIBUTING.md: add guide for first-time contributors, 2018-03-01) there were _two_ links added for PuTTY, one being the correct, official one, and the other an official-looking one owned by a third-party. Let's only use the official one. Original-patch-by: @jsoref in https://github.com/microsoft/git/pull/774
Thu, Jul 10, 2025, 07:48:46 AM GMT
Replace experimental path walk feature with upstream version (#5689) This reverts the experimental version of the `git repack --path-walk` feature and replaces it with the version that recently merged with upstream. It includes `fixup!` commits for the reverts of the previous feature for easy reduction in the branch thicket during the 2.51.0 release window. > Note: In the current version, I have not performed any local validation, only resolved one text merge conflict.
Wed, Jul 2, 2025, 09:44:54 AM GMT
Merge tag 'v2.50.1' Git 2.50.1 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Mon, Jun 30, 2025, 09:26:00 AM GMT
mingw: support Windows Server 2016 again It was reported to the Git for Windows project that a simple `git init` fails on Windows Server 2016: D:\Dev\test> git init error: could not write config file D:/Dev/test/.git/config: Function not implemented fatal: could not set 'core.repositoryformatversion' to '0' According to https://endoflife.date/windows-server, Windows Server 2016 is officially supported for another one-and-a-half years as of time of writing, so this is not good. The culprit is the `mingw_rename()` changes that try to use POSIX semantics when available, but fail to fall back properly on Windows Server 2016. This fixes https://github.com/git-for-windows/git/issues/5695. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Mon, Jun 16, 2025, 07:26:56 PM GMT
Reapply "bswap.h: add support for built-in bswap functions" The `bswap.h` header was introduced to fix the Windows/ARM64 build. Unfortunately, this broke big Endian machines. Instead of fixing it properly, upstream Git simply reverted the commit in 1c62df0abe3d (Revert "bswap.h: add support for built-in bswap functions", 2025-06-12), re-breaking the Windows/ARM64 build. Let's re-un-break the Windows/ARM64 build by reverting 1c62df0abe3d (Revert "bswap.h: add support for built-in bswap functions", 2025-06-12). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Mon, Jun 16, 2025, 07:26:56 PM GMT
Reapply "bswap.h: add support for built-in bswap functions" The `bswap.h` header was introduced to fix the Windows/ARM64 build. Unfortunately, this broke big Endian machines. Instead of fixing it properly, upstream Git simply reverted the commit in 1c62df0abe3d (Revert "bswap.h: add support for built-in bswap functions", 2025-06-12), re-breaking the Windows/ARM64 build. Let's re-un-break the Windows/ARM64 build by reverting 1c62df0abe3d (Revert "bswap.h: add support for built-in bswap functions", 2025-06-12). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Wed, Jun 11, 2025, 06:26:44 AM GMT
Merge 'readme' into HEAD Add a README.md for GitHub goodness. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Wed, Jun 11, 2025, 01:02:22 PM GMT
Fix Coverity builds (#5672) As of three months ago, Git for Windows' [Coverity builds fail](https://github.com/git-for-windows/git/actions/workflows/coverity.yml?query=branch%3Amain). The reason is most likely the most recent release, 2025.3. Its [release notes](https://documentation.blackduck.com/bundle/coverity-docs/page/webhelp-files/relnotes_latest.html) do not shed any light into the issue (and does not mention that they bundle JDK20 and JDK22 in addition to JRE, because what's better than a single Java installation: three, right?). My investigation turned up `.dll` files that are located in Coverity's `bin/` directory which have the same name as `.dll` files in Git for Windows' SDK. As a consequence, the former override the latter and throw off MSYS2's logic to find the MSYS2 root directory given the location of certain `.dll` files. This PR fixes this issue, and while at it, enhances the Coverity workflow to print out the build log in case of failure.
Wed, Jun 11, 2025, 08:19:36 AM GMT
Create an issue form (#5238) This fixes #5229 (Issue templates no longer working): Seems that the templates need to be put into `.github/ISSUE_TEMPLATE/`, and that `.github/ISSUE_TEMPLATE.md` does not work anymore. We could use the opportunity to turn this into [an issue form](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-templates) (which would make it much less likely to get those issues with all the placeholders left as-are, I'd hope).
Thu, Jun 5, 2025, 11:20:05 AM GMT
mingw: avoid the comma operator (#5660) The pattern `return errno = ..., -1;` is observed several times in `compat/mingw.c`. It has served us well over the years, but now clang starts complaining: ``` compat/mingw.c:723:24: error: possible misuse of comma operator here [-Werror,-Wcomma] 723 | return errno = ENOSYS, -1; | ^ ``` See for example [this failing workflow run](https://github.com/git-for-windows/git-sdk-arm64/actions/runs/15457893907/job/43513458823#step:8:201). Let's appease clang (and also reduce the use of the no longer common comma operator).