Tags: bwijen/git
Tags
Git for Windows v2.8.2
Changes since Git for Windows v2.8.1 (April 4th 2016)
New Features
• Comes with Git v2.8.2.
• Starting with version 2.8.2, Git for Windows is also published as a
NuGet package.
• Comes with Git Credential Manager v1.3.0.
Bug Fixes
• FSCache is now enabled by default even when upgrading from previous
Git for Windows versions.
• We now add git.exe to the PATH by default even when upgrading from
previous Git for Windows versions.
• Git GUI now sets author information correctly when amending.
• OpenSSL received a critical update to version 1.0.2h.
Git for Windows v2.8.1
Changes since Git for Windows v2.8.0 (March 29th 2016)
New Features
• Comes with Git v2.8.1.
• The Git for Windows project updated its contributor guidelines to
the Contributor Covenant 1.4.
Bug Fixes
• Git's default editor (vim) is no longer freezing in CMD windows.
• GIT_SSH (and other executable paths that Git wants to spawn) can
now contain spaces.
Git for Windows v2.8.0
Changes since Git for Windows v2.7.4 (March 18th 2016)
New Features
• Comes with Git v2.8.0.
• Comes with the Git Credential Manager v1.2.2.
• The FSCache feature (which was labeled experimental for quite some
time) is now enabled by default.
• Git is now added to the PATH by default (previously, the default
was for Git to be available only from Git Bash/CMD).
• The installer now offers to launch the Git Bash right away.
Bug Fixes
• The previous workaround for the blurred link to the Git Credential
Manager was fixed so that the link is neither blurry nor
overlapping.
• The installer now changes the label of the Next button to Install
on the last wizard page before installing.
Git for Windows v2.7.4
Changes since Git for Windows v2.7.3 (March 15th 2016)
New Features
• Comes with Git 2.7.4.
Bug Fixes
• The Git Credential Manager hyperlink in the installer is no longer
blurred.
Git for Windows v2.7.3
Changes since Git for Windows v2.7.2 (February 23rd 2016)
New Features
• Git for Windows now ships with the Git Credential Manager for
Windows.
Bug Fixes
• We now handle UTF-8 merge and squash messages correctly in Git GUI.
• When trying to modify a repository config outside of any Git
worktree, git config no longer creates a .git/ directory but prints
an appropriate error message instead.
• A new version of Git for Windows' SDK was released.
• We no longer show asterisks when reading the username for
credentials.
Git for Windows v2.7.2
Changes since Git for Windows v2.7.1(2) (February 12th 2016)
New Features
• Git for Windows' SDK version 1.0.2 has been released.
• The "list references" window of gitk is now wider by default.
• Comes with Git 2.7.2.
Bug Fixes
• The user is now presented with a nice error message when calling
node while node.exe is not in the PATH (this bug also affected
other interactive console programs such as python and php).
• The arrow keys are respected again in gitk.
• When a too-long path is encountered, git clean -dfx no longer
aborts quietly.
• Git GUI learned to stage lines appended to a single-line file.
• When launching C:\Program Files\Git\bin\bash -l -i in a cmd window
and pressing Ctrl+C, the console is no longer corrupted
(previously, the bash.exe redirector would terminate and both cmd &
Bash would compete for user input).
Git for Windows v2.7.1(2)
Changes since Git for Windows v2.7.1 (February 6th 2016)
New Features
• The context menu items in the explorer now show icons.
Bug Fixes
• A bug was fixed where worktrees would forget their location e.g.
after an interactive rebase.
• Thanks to Eric Lawrence and Martijn Laan, our installer sports a
better way to look for system files now.
Git for Windows v2.7.1
Changes since Git for Windows v2.7.0(2) (February 2nd 2016)
New Features
• Comes with Git 2.7.1.
Bug Fixes
• Git GUI now starts properly even when the working directory
contains non-ASCII characters.
• We forgot to enable Address Space Layout Randomization and Data
Execution Prevention on our Git wrapper, and this is now fixed.
• A bug in one of the DLLs used by Git for Windows was fixed that
prevented Git from working properly in 64-bit setups where the
FLG_LDR_TOP_DOWN global flag is set.
PreviousNext