{"thread":{"id":"47770","subject":"[ANNOUNCE] Git for Windows 2.16.1(3)","startedAt":"2018-02-06T15:38:16Z","lastAt":"2018-02-06T16:17:34Z","messageCount":2,"participants":["Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"338517","messageId":"20180206153802.14064-1-johannes.schindelin@gmx.de","threadId":"47770","inReplyTo":null,"subject":"[ANNOUNCE] Git for Windows 2.16.1(3)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2018-02-06T15:38:02Z","receivedAt":"2018-02-06T15:38:16Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Dear Git users,\n\nIt is my pleasure to announce that Git for Windows 2.16.1(3) is available from:\n\n\thttps://git-for-windows.github.io/\n\nChanges since Git for Windows v2.16.1(2) (February 2nd 2018)\n\nNew Features\n\n  * Git for Windows' SDK packages are now hosted on Azure Blobs, fixing\n    part of issue #1479.\n  * Comes with perl-Net-SSLeay v1.84.\n\nBug Fixes\n\n  * When http.sslBackend is not configured (e.g. in portable Git or\n    MinGit), fetch/push operations no longer crash.\n  * On Windows 7 and older, Git for Windows v2.16.1(2) was no longer\n    able to spawn any processes (e.g. during fetch/clone). This\n    regression has been fixed.\n  * The Perl upgrade in v2.16.1(2) broke git send-email; This has been\n    fixed by updating the Net-SSLeay Perl module.\n\nFilename | SHA-256\n-------- | -------\nGit-2.16.1.3-64-bit.exe | 27cec5113e2572d22336150afec337fc94627b330ebeec2a61b8bb447a6301ea\nGit-2.16.1.3-32-bit.exe | ad1fca7ac33326378b8be187d4595f50c72bd8ad00b277807fc091c16bd9796c\nPortableGit-2.16.1.3-64-bit.7z.exe | bcb3ca27ae151313ab369d9f39b018129035d7fa018fa0df364424b6e22be4d3\nPortableGit-2.16.1.3-32-bit.7z.exe | ae4cf93c391c66698856b8b38ba3a42e7fcc7141f61531562134f72b1c014f36\nMinGit-2.16.1.3-64-bit.zip | a3ee17301ef563349f9936e68beb996c747079afc883e4e40615931e032905fd\nMinGit-2.16.1.3-32-bit.zip | c46c6697906a1a85f784c7cf6e0385689ae3105bc8fe99b20c3a70ac73ab8e9e\nMinGit-2.16.1.3-busybox-64-bit.zip | 630bb6d79c9b0f64c81046208d00a41edb2540bd99a2626c5fdaf0550cdb1a9e\nMinGit-2.16.1.3-busybox-32-bit.zip | 3ff6f9e936d837d6f319bdb1ea4f0fcc9ff6bc203f9de1987538313686574f1b\nGit-2.16.1.3-64-bit.tar.bz2 | c7c4f9a9205e85977475698732484c6524d8b381f03ceaf04f35bd6f89bce389\nGit-2.16.1.3-32-bit.tar.bz2 | 8ed49c8008728c70e82436d8c1cafb23cb2ee1f7b01d2e97a7e626d2438a0cd1\n\nCiao,\nJohannes\n"},{"id":"338519","messageId":"nycvar.QRO.7.76.6.1802061712430.35@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz","threadId":"47770","inReplyTo":"20180206153802.14064-1-johannes.schindelin@gmx.de","subject":"Re: [ANNOUNCE] Git for Windows 2.16.1(3)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2018-02-06T16:17:25Z","receivedAt":"2018-02-06T16:17:34Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Dear Git for Windows SDK users,\n\n[This mail only concerns the *SDK* of Git for Windows, i.e. the build\nenvironment to work on, and contribute to, Git for Windows.]\n\nOn Tue, 6 Feb 2018, Johannes Schindelin wrote:\n\n> Changes since Git for Windows v2.16.1(2) (February 2nd 2018)\n> \n> New Features\n> \n>   * Git for Windows' SDK packages are now hosted on Azure Blobs, fixing\n>     part of issue #1479.\n\nTo clarify what this means for any developer who wants to update or\ninstall a Git for Windows SDK, here is some guidance.\n\n# Fixing existing SDKs\n\nYou can fix your existing SDK (if you installed it successfully before\nFriday, February 2nd 2018) by downloading either\n\n- https://wingit.blob.core.windows.net/x86-64/git-extra-1.1.241.91af289c6-1-x86_64.pkg.tar.xz\n  for 64-bit SDKs, or\n- https://wingit.blob.core.windows.net/x86-64/git-extra-1.1.241.91af289c6-1-i686.pkg.tar.xz\n  for 32-bit SDKs,\n\nand then executing `pacman -U <downloaded-file>`. This will have the main\neffect of updating your `/etc/pacman.conf` so that a subsequent `pacman\n-Syu` will find the new home of Git for Windows' Pacman repositories.\n\n# Initializing a new SDK\n\nIf you did not yet have a working SDK, the [installer as per Git for\nWindows' home page](https://gitforwindows.org/#download-sdk) will not work\n(I hope that we get all of this sorted out this week).\n\nThe idea is to support a completely new, more robust method of obtaining a\nworking SDK:\n\n```cmd\ngit clone --depth 1 https://github.com/git-for-windows/git-sdk-64\n```\n\n(or `.../git-sdk-32` for 32-bit setups) and then call `git-bash.exe` in\nthe top-level directory of the checkout.\n\n(These repositories are essentially synchronized by a scheduled job\nrunning on Visual Studio Team Services, and the set of installed packages\nwas chosen so as to support the most common operations developer would\nwant to perform in a Git for Windows SDK.)\n\nThis does already work!\n\nBut you still have to clone https://github.com/git-for-windows/git\nmanually for the time being (preferred checkout location: /usr/src/git),\nand maybe also https://github.com/git-for-windows/build-extra.\n\n## Future work\n\nI plan on doing a couple more things in the git-sdk-* repositories, and\nevery bit of help with those tasks will be greatly appreciated:\n\n- add a `README.md` explaining the purpose, the most common operations,\n  context and design\n- modify\n  [`/etc/profile.d/git-sdk.sh`](https://github.com/git-for-windows/build-extra/blob/master/git-extra/git-sdk.sh)\n  so that it auto-initializes the `git`, `build-extra`, `MINGW-packages` and\n  `MSYS2-packages` worktrees in `/usr/src`: they should only be `git\n  init`'ed and `git add remote origin ...`, but *not* fetching anything yet.\n  They can then be initialized on demand by e.g. `git -C /usr/src/git pull\n  origin master`\n- ensure that a regular clone works, especially 32-bit, where some of the\n  files seem to be committed with incorrect line endings\n- modify the git-sdk-installer to use the new method instead\n- maybe add an `/etc/motd` that describes how to build stuff, how to\n  bundle a custom installer, how to keep the SDK up-to-date, etc. Or maybe\n  a helper. Dunno.\n\nThis blurb was copy-edited from\nhttps://github.com/git-for-windows/git/issues/1479#issuecomment-363452826\n\nFor updates on the Git for Windows SDK front, please follow that ticket!\n\nThanks,\nJohannes\n"}]}