标签使您能够将历史中的特定点标记为重要点
-
v2.17.1.windows.2
a60968cf · ·Git for Windows v2.17.1(2) Changes since Git for Windows v2.17.1 (May 29th 2018) New Features * Comes with Git Credential Manager v1.16.1. * Comes with Git LFS v2.4.2. Bug Fixes * This release really contains Git v2.17.1.
-
v2.17.1.windows.1
4a158e75 · ·Git for Windows v2.17.1 Changes since Git for Windows v2.17.0 (April 3rd 2018) New Features * Comes with Git v2.17.1. * Comes with Perl v5.26.2. * The installer now offers VS Code Insiders as option for Git's default editor if it is installed. * The vim configuration was modernized. * Comes with cURL v7.60.0. * Certain errors, e.g. when pushing failed due to a non-fast-forwarding change, are now colorful. * Comes with cURL v7.60.0. * Comes with Git LFS v2.4.1. Bug Fixes * Fixed an issue with recursive clone (CVE 2018-11235). * Aliases that expand to shell commands can now take arguments containing curly brackets. * Ctrl+C is now handled in Git Bash in a sophisticated way: it emulates the way Ctrl+C is handled in Git CMD, but in a fine-grained way. * Based on the the new Ctrl+C handling in Git Bash, pressing Ctrl+C while git log is running will only stop Git from traversing the commit history, but keep the pager running. * Git was fixed to work correctly in Docker volumes inside Windows containers. * Tab completion of git status -- <partial-path> is now a lot faster. * Git for Windows now creates directory symlinks correctly when asked to. * The option to disable revocation checks with Secure Channel which was introduced in v2.16.1(2) now really works. * Git no longer enters an infinite loop when misspelling git status as, say, git Status. -
v2.11.1.mingit-prerelease.3
7eb88f39 · ·MinGit v2.11.1 prerelease 3 Changes since MinGit v2.11.1 prerelease 2 (Aug 17th 2017) Bug Fixes * A specially-crafted .gitmodules could cause problems.
-
v2.14.4.windows.1
46546482 · ·MinGit for Windows v2.14.4 This is a MinGit-only release; compared to v2.14.3(2), it only adds the fix for the recursive submodule clone bug.
-
v2.17.0.windows.1
e7621d89 · ·Git for Windows v2.17.0 Changes since Git for Windows v2.16.3 (March 23rd 2018) New Features * Comes with Git v2.17.0. * Comes with OpenSSL v1.0.2o. * Comes with Git Credential Manager v1.15.2. * Comes with OpenSSH v7.7p1. Bug Fixes * When git.exe is called with an invalid subcommand, it no longer complains about file handles. -
v2.16.3.windows.1
5d726e05 · ·Git for Windows v2.16.3 Changes since Git for Windows v2.16.2 (February 20th 2018) New Features * Comes with Git v2.16.3. * When choosing to "Use Git from the Windows Command Prompt" (i.e. add only the minimal set of Git executables to the PATH), and when choosing the Git LFS component, Git LFS is now included in that minimal set. This makes it possible to reuse Git for Windows' Git LFS, say, from Visual Studio. * Comes with gawk v4.2.1. * In conjunction with the FSCache feature, git checkout is now a lot faster when checking out a lot of files. * Comes with Git LFS v2.4.0. * Comes with Git Credential Manager v1.15.0. * Comes with cURL v7.59.0. * The Git for Windows SDK can now be "installed" via git clone --depth=1 https://github.com/git-for-windows/git-sdk-64. * The tar utility (included as a courtesy, not because Git needs it) can now unpack .tar.xz archives. Bug Fixes * When a TERM is configured that Git for Windows does not know about, Bash no longer crashes. * The regression where gawk stopped treating Carriage Returns as part of the line endings was fixed. * When Git asks for credentials via the terminal in a Powershell window, it no longer fails to do so. * The installer is now more robust when encountering files that are in use (and can therefore not be overwritten right away). * The included find and rm utilities no longer have problems with deeply nested directories on FAT drives. * The cygpath utility included in Git for Windows now strips trailing slashes when normalizing paths (just like the Cygwin version of the utility; this is different from how MSYS2 chooses to do things). * The certificates of HTTPS proxies configured via http.proxy are now validated against the ca-bundle.crt correctly.