You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The auto-updater now shows Git for Windows icon in the notification also on Windows/ARM64.
git clone/git fetch now deals more gracefully with directory / file conflicts when the files backend is used for ref storage, by failing only the ones that are involved in the conflict while allowing others. This is a regression in Git v2.51.0 that was reported in Git for Windows and independently also to the Git mailing list. This was fixed by merging Git's topic branch kn/refs-files-case-insensitive.
Support for pathspecs in diff --no-indexwas somewhat buggy, which has been fixed.
git sparse-checkout subcommand learned a new clean action to prune otherwise unused working-tree files that are outside the areas of interest. An earlier version of this had been integrated into Microsoft Git already. This was fixed by merging Git's topic branch ds/sparse-checkout-clean.
git rebase -i failed to clean-up the commit log message when the command commits the final one in a chain of "fixup" commands, which has been corrected. Backported from Git's topic branch pw/rebase-i-cleanup-fix.
git subtree did not work correctly when splitting squashed subtrees, which has been improved. Backported from Git's topic branch cs/subtree-squash-split-fix.
Some among git add -p and friends ignored color.diff and/or color.ui configuration variables, which is an old regression, which has been corrected. This was fixed by merging Git's topic branch jk/add-i-color.
A corner-case bug in git log -L... has been corrected. This was fixed by merging Git's topic branch sg/line-log-boundary-fixes.
A broken or malicious git fetch can say that it has the same object for many many times, and the upload-pack serving it can exhaust memory storing them redundantly, which has been corrected. This was fixed by merging Git's topic branch ps/upload-pack-oom-protection.
Fixes multiple crashes around midx write-out codepaths. This was fixed by merging Git's topic branch ds/midx-write-fixes.
git repack --path-walk lost objects in some corner cases, which has been corrected. This was fixed by merging Git's topic branch ds/path-walk-repack-fix.
Under a race against another process that is repacking the repository, especially a partially cloned one, git fetch may mistakenly think some objects we do have are missing, which has been corrected. This was fixed by merging Git's topic branch jk/fetch-check-graph-objects-fix.
Various options to git diff that makes comparison ignore certain aspects of the differences (like "space changes are ignored", "differences in lines that match these regular expressions are ignored") did not work well with --name-only and friends. This was fixed by merging Git's topic branch ly/diff-name-only-with-diff-from-content.
git diff --no-index run inside a subdirectory under control of a Git repository operated at the top of the working tree and stripped the prefix from the output, and oddballs like "-" (stdin) did not work correctly because of it. Correct the set-up by undoing what the set-up sequence did to the current working directory and prefix. This was fixed by merging Git's topic branch jc/diff-no-index-in-subdir.
Various bugs about rename handling in "ort" merge strategy have been fixed. This was fixed by merging Git's topic branch en/ort-rename-fixes.
git push had a code path that led to BUG() but it should have reported a regular failure, as it is a response to a usual but invalid end-user action to attempt pushing an object that does not exist. This was fixed by merging Git's topic branch dl/push-missing-object-error.
git refs migrate to migrate the reflog entries from a refs backend to another had a handful of bugs squashed. This was fixed by merging Git's topic branch ps/reflog-migrate-fixes.
During interactive rebase, using drop on a merge commit lead to an error, which was incorrect. This was fixed by merging Git's topic branch js/rebase-i-allow-drop-on-a-merge.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Changes since Git for Windows v2.51.0 (August 19th 2025)
New Features
failed to read data from server: SEC_E_CONTEXT_EXPIRED (0x80090317)under certain circumstances. Also included: a back-port of a fix for a bug where connection failures were mistakenly reported as time-outs.Bug Fixes
git clone/git fetchnow deals more gracefully with directory / file conflicts when the files backend is used for ref storage, by failing only the ones that are involved in the conflict while allowing others. This is a regression in Git v2.51.0 that was reported in Git for Windows and independently also to the Git mailing list. This was fixed by merging Git's topic branchkn/refs-files-case-insensitive.diff --no-indexwas somewhat buggy, which has been fixed.git sparse-checkoutsubcommand learned a newcleanaction to prune otherwise unused working-tree files that are outside the areas of interest. An earlier version of this had been integrated into Microsoft Git already. This was fixed by merging Git's topic branchds/sparse-checkout-clean.git rebase -ifailed to clean-up the commit log message when the command commits the final one in a chain of "fixup" commands, which has been corrected. Backported from Git's topic branchpw/rebase-i-cleanup-fix.git subtreedid not work correctly when splitting squashed subtrees, which has been improved. Backported from Git's topic branchcs/subtree-squash-split-fix.git add -pand friends ignoredcolor.diffand/orcolor.uiconfiguration variables, which is an old regression, which has been corrected. This was fixed by merging Git's topic branchjk/add-i-color.git log -L...has been corrected. This was fixed by merging Git's topic branchsg/line-log-boundary-fixes.git fetchcan say that it has the same object for many many times, and the upload-pack serving it can exhaust memory storing them redundantly, which has been corrected. This was fixed by merging Git's topic branchps/upload-pack-oom-protection.ds/midx-write-fixes.git repack --path-walklost objects in some corner cases, which has been corrected. This was fixed by merging Git's topic branchds/path-walk-repack-fix.git fetchmay mistakenly think some objects we do have are missing, which has been corrected. This was fixed by merging Git's topic branchjk/fetch-check-graph-objects-fix.git diffthat makes comparison ignore certain aspects of the differences (like "space changes are ignored", "differences in lines that match these regular expressions are ignored") did not work well with--name-onlyand friends. This was fixed by merging Git's topic branchly/diff-name-only-with-diff-from-content.git diff --no-indexrun inside a subdirectory under control of a Git repository operated at the top of the working tree and stripped the prefix from the output, and oddballs like "-" (stdin) did not work correctly because of it. Correct the set-up by undoing what the set-up sequence did to the current working directory and prefix. This was fixed by merging Git's topic branchjc/diff-no-index-in-subdir.en/ort-rename-fixes.git pushhad a code path that led toBUG()but it should have reported a regular failure, as it is a response to a usual but invalid end-user action to attempt pushing an object that does not exist. This was fixed by merging Git's topic branchdl/push-missing-object-error.git refs migrateto migrate the reflog entries from a refs backend to another had a handful of bugs squashed. This was fixed by merging Git's topic branchps/reflog-migrate-fixes.dropon a merge commit lead to an error, which was incorrect. This was fixed by merging Git's topic branchjs/rebase-i-allow-drop-on-a-merge.This discussion was created from the release Git for Windows v2.51.0.windows.2.
Beta Was this translation helpful? Give feedback.
All reactions