3 ms·

The initial Git for Windows 2.17.1 releases published on GitHub earlier today [0] apparently didn't include the patch. So just a heads up if you updated right a

The initial Git for Windows 2.17.1 releases published on GitHub earlier today [0] apparently didn't include the patch. So just a heads up if you updated right after this was published: You probably want to make sure you have the fixed version (2.17.1.windows.2) [1] Not sure why the erroneous releases haven't been removed? Seems a bit confusing. [0] https://github.com/git-for-windows/git/releases/tag/v2.17.1.windows.1 https://github.com/git-for-windows/git/releases/tag/v2.17.1.... [1] https://github.com/git-for-windows/git/releases/tag/v2.17.1.windows.2 https://github.com/git-for-windows/git/releases/tag/v2.17.1....

mappu 8y ago
The link on https://git-scm.com/ https://git-scm.com/ still points to the old 2.17.0. Chocolatey has the original 2.17.1, the 2.17.1-2 update is not yet approved. Cygwin still only has 2.17.0-1. I wonder whether they were even part of the embargo.
- runesoerensen 8y ago
  For some reason git-scm.com is almost always slow at updating links to new Git for Windows releases. I usually just track the repository's atom feed [0] and download urgent updates directly from there (git-scm.com eventually links to the releases published on GitHub anyway). [0] https://github.com/git-for-windows/git/releases.atom https://github.com/git-for-windows/git/releases.atom Edit: The Git 2.17.1.2 Chocolatey package has now been approved https://chocolatey.org/packages/git/2.17.1.2 https://chocolatey.org/packages/git/2.17.1.2