首页
开源
资讯
活动
开源许可证
软件工程云服务
软件代码质量检测云服务
持续集成与部署云服务
社区个性化内容推荐服务
贡献审阅人推荐服务
群体化学习服务
重睛鸟代码扫描工具
登录
注册
代码拉取完成,页面将自动刷新
Watch
1
Star
0
Fork
0
lincoln7406
/
git
Fork 仓库
加载中
取消
确认
代码
Issues
0
Pull Requests
0
Wiki
0
统计
标签
标签名
描述
提交信息
操作
v2.26.0-rc0.windows.1
Git for Windows v2.26.0-rc0
235cd37
2020-03-06 20:55
下载
v2.25.1.windows.1
Git for Windows v2.25.1
cceb69d
2018-06-07 14:45
下载
v2.25.0.windows.1
Git for Windows v2.25.0 Changes since Git for Windows v2.24.1(2) (December 10th 2019) New Features * Comes with Git v2.25.0. * Comes with GNU Privacy Guard v2.2.19. * Comes with Git LFS v2.9.2. * When upgrading Git for Windows, by default the installer now only shows pages with previously-unseen options. * Comes with cURL v7.68.0. Bug Fixes * The startup file for GNU nano, which had been included with DOS line endings (and therefore upset nano) is now included with Unix line endings again. * Git for Windows now fails as expected when trying to check out files with illegal characters in their file names. * Git now works properly when inside a symlinked work tree. * Repositories with old commits containing backslashes in file names can now be fetched/cloned again (but Git will still refuse to check out files with backslashes in their file names). * Git GUI can now deal with uninitialized submodules (this was a Windows-specific bug). * It is again possible to clone repositories where some past revision contained file names containing backslashes (Git will of course still refuse to check out such revisions).
7c71c85
2018-06-07 14:45
下载
v2.25.0-rc2.windows.1
Third preview for v2.25.0
a4e27d9
2018-06-07 14:45
下载
v2.25.0-rc1.windows.1
Second preview for v2.25.0
d16625c
2018-06-07 14:45
下载
v2.25.0-rc0.windows.1
Early preview of Git for Windows v2.25.0.
2249a76
2018-06-07 14:45
下载
v2.24.1.windows.2
Git for Windows v2.24.1(2) Changes since Git for Windows v2.24.0(2) (November 6th 2019) This is a security bug release that fixes CVE-2019-1348, CVE-2019-1349, CVE-2019-1350, CVE-2019-1351, CVE-2019-1352, CVE-2019-1353, CVE-2019-1354, CVE-2019-1387, and CVE-2019-19604. New Features * Comes with Git v2.24.1. * Comes with tig v2.5.0. * Comes with patch level 4 of the MSYS2 runtime (Git for Windows flavor) based on Cygwin 3.0.7. * The command-line options of git-bash.exe are now documented (call git help git-bash). * Comes with Git LFS v2.9.1. * Comes with cURL v7.67.0. * Comes with GNU Privacy Guard v2.2.18. Bug Fixes * MinGit no longer overrides an installed Git for Windows' system gitconfig. * The "Check daily for updates" feature uses the Action Center again. * When associating .sh files with Git Bash to allow running them by double-clicking them in the Windows Explorer, shell scripts with non-ASCII characters in their file name are now supported.
992f077
2018-06-07 14:45
下载
v2.24.0.windows.2
Git for Windows v2.24.0(2) Changes since Git for Windows v2.24.0 (November 4th 2019) New Features * Comes with cURL v7.67.0. Bug Fixes * Using http.extraHeader no longer results in spurious crashes. * The /proc/{stdin,stdout,stderr} pseudo-symlinks are now installed properly even with non-US locales. * A bug was fixed that prevented gitk from refreshing after new changes were committed.
02af2cc
2019-11-05 07:11
下载
v2.24.0.windows.1
Git for Windows v2.24.0 Changes since Git for Windows v2.23.0 (August 17th 2019) Note! As a consequence of making git config --system work as expected, the location of the system config is now C:\Program Files\Git\etc\ gitconfig (no longer split between C:\Program Files\Git\mingw64\etc\ gitconfig and C:\ProgramData\Git\config), and likewise the location of the system gitattributes is now C:\Program Files\Git\etc\gitattributes (no longer C:\Program Files\Git\mingw64\etc\gitattributes). Any manual modifications to C:\ProgramData\Git\config need to be ported manually. New Features * Comes with Git v2.24.0. * Comes with cURL v7.66.0. * Comes with Git Credential Manager v1.20.0. * Comes with OpenSSH v8.1p1. * Comes with OpenSSL v1.1.1d. * Comes with Git LFS v2.9.0. Bug Fixes * The shell construct <(<command>), which was broken in v2.23.0 (/dev /fd/<n>: no such file or directory), was fixed. * The default config no longer skips git-lfs downloads. * Starting with cURL v7.66.0, $HOME/.netrc can be used instead of $HOME/_netrc (but it will still fall back to looking for the latter). * The installer's "ProductVersion" is now consistent with older Git for Windows versions'. * Makes git config --system work like you think it should. * The (still experimental) built-in git add -p no longer gets confused about incomplete lines (i.e. a file's l last line that does not end in a Line Feed). * A buffer overrun in the code to determine which files need to be marked as hidden was plugged. * The support for sendpack.sideband that was removed by mistake was re-introduced, to support git push via the git:// protocol again. * git stash no longer records skip-worktree files as deleted after resolving merge conflicts in them. * The Git for Windows installer no longer complains about a downgrade when upgrading from an -rc version, i.e. from a pre-release leading up to the next major version.
6a3fa2a
2018-06-07 14:45
下载
v2.24.0-rc2.windows.1
Third preview for v2.24.0
9356bff
2018-06-07 14:45
下载
v2.23.0.windows.2
MinGit for Windows v2.23.0(2) Changes since Git for Windows v2.23.0 (August 17th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * The Azure Pipeline was adjusted for changes in Homebrew that are outside of Git's control. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
a17d949
2019-10-24 01:56
下载
v2.22.0.windows.2
MinGit for Windows v2.22.0(2) Changes since Git for Windows v2.22.0 (June 8th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * The Azure Pipeline was adjusted for changes in Homebrew that are outside of Git's control. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
028e037
2019-10-24 01:56
下载
v2.21.0.windows.4
MinGit for Windows v2.21.0(4) Changes since MinGit v2.21.0(4) (August 17th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * The Azure Pipeline was adjusted for changes in Homebrew and Cygwin that are outside of Git's control. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
a1f830a
2019-10-24 01:56
下载
v2.19.2.windows.4
MinGit for Windows v2.19.2(4) Changes since MinGit v2.19.2(3) (August 17th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * The Azure Pipeline now runs the Windows tests in parallel, to make validation of newer MinGit versions faster. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
b7c5246
2019-10-24 01:56
下载
v2.24.0-rc1.windows.1
Second preview for v2.24.0
b1b9387
2018-06-07 14:45
下载
v2.11.1.mingit-prerelease.6
MinGit v2.11.1 prerelease 6 Changes since MinGit v2.11.1 prerelease 5 (August 17th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * An Azure Pipelines build definition has been added. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
1b4321e
2019-10-24 01:56
下载
v2.14.4.windows.5
MinGit for Windows v2.14.4(5) Changes since MinGit for Windows v2.14.4(5) (August 17th 2019) Enhancements: * There is only one system gitconfig now (no more `C:\ProgramData\Git\config`), and it is in the top-level `etc` directory. * An Azure Pipelines build definition has been added. Bug Fixes * CVE-2019-1348: The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths. * CVE-2019-1349: When submodules are cloned recursively, under certain circumstances Git could be fooled into using the same Git directory twice. We now require the directory to be empty. * CVE-2019-1350: Incorrect quoting of command-line arguments allowed remote code execution during a recursive clone in conjunction SSH URLs. * CVE-2019-1351: While the only permitted drive letters for physical drives on Windows are letters of the US-English alphabet, this restriction does not apply to virtual drives assigned via subst <letter>: <path>. Git mistook such paths for relative paths, allowing writing outside of the worktree while cloning. * CVE-2019-1352: Git was unaware of NTFS Alternate Data Streams, allowing files inside the .git/ directory to be overwritten during a clone. * CVE-2019-1353: When running Git in WSL while accessing a working directory on a regular Windows drive, none of the NTFS protections were active. * CVE-2019-1354: Filenames on Linux/Unix can contain backslashes. On Windows, backslashes are directory separators. Git did not use to refuse to write out tracked files with such filenames. * CVE-2019-1387: Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
5089fc7
2019-10-24 01:56
下载
v2.24.0-rc0.windows.1
Early preview of Git for Windows v2.24.0.
51b78e6
2018-06-07 14:45
下载
v2.14.4.windows.4
MinGit for Windows v2.14.4(4) Changes since MinGit v2.14.4(3) (August 13th 2019) Bug Fixes * When C:\ProgramData\Git\config's ownership is validated before it is used, a non-existing file does not trigger a warning about dubious ownership any longer.
401020d
2019-08-16 04:19
下载
v2.21.0.windows.3
MinGit for Windows v2.21.0(3) Changes since MinGit v2.21.0(2) (August 13th 2019) Bug Fixes * When C:\ProgramData\Git\config's ownership is validated before it is used, a non-existing file does not trigger a warning about dubious ownership any longer.
cbac647
2019-08-16 04:19
下载
下载
请输入验证码,防止盗链导致资源被占用
取消
下载