Tags: rimrul/git
Tags
Git for Windows 2.5.2 (Release 2) The following bugs were fixed since Git for Windows 2.5.2: • The Git GUI can be launched from the Start menu again. • It now works to call git add -p -- . when there is a large number of files. • The Arrow keys can be used in the Bash history again when run in the Windows console. • Tab completion in the context of a large Active Directory is no longer slow.
Git for Windows 2.5.2 The changes since Git for Windows 2.5.1 are: New Features • Comes with Git 2.5.2 • Alternates can now point to UNC paths, i.e. network drives. Bug fixes • The MSys2 runtime was taught not to look hard for groups, speeding up Git Bash's startup time. • A work around was added for issues when installing 32-bit Git for Windows on 64-bit Windows 10. • The installer no longer freezes when there are interactive commands in the user's .profile. • git rebase --skip was speeded up again. • The redirector in /bin/bash.exe now adjusts the PATH environment variable correctly (i.e. so that Git's executables are found) before launching the real Bash, even when called without --login. • When installing Git for Windows to a location whose path is longer than usual, Git commands no longer trigger occasional Bad address errors. • Git no longer asks for a DVD to be inserted again when one has been ejected from the D: drive.
Git for Windows 2.5.1 In addition to synchronizing with Git 2.5.1, this release also contains the following bug fixes: * Backspace works with ConHost-based (`cmd.exe`) terminal. * When there is a `~/.bashrc` but no `~/.bash_profile`, the latter will be created automatically. * When calling a non-login shell, the prompt now works. * The text in the installer describing the terminal emulator options is no longer cut off. * The `connect.exe` tool to allow SSH connections via HTTP/HTTPS/SOCKS proxies is included in Git for Windows again, as it was in Git for Windows 1.x. * The `LANG` variable is no longer left unset (which caused troubles with vim). * `call start-ssh-agent` no longer spits out bogus lines. * It is now possible even behind NTLM-authenticated proxies to install Git for Windows' SDK. * We can handle the situation now when the first `$PATH` elements point outside of Git for Windows' `bin/` directories and contain `.dll` files that interfere with our own (e.g. PostgreSQL's `libintl-8.dll`).
PreviousNext