{"thread":{"id":"58293","subject":"[ANNOUNCE] Git for Windows 2.37.2","startedAt":"2022-08-11T21:43:05Z","lastAt":"2022-08-15T16:08:23Z","messageCount":6,"participants":["Johannes Schindelin","Junio C Hamano","Victoria Dye"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"461102","messageId":"20220811214252.4351-1-johannes.schindelin@gmx.de","threadId":"58293","inReplyTo":null,"subject":"[ANNOUNCE] Git for Windows 2.37.2","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-08-11T21:42:52Z","receivedAt":"2022-08-11T21:43:05Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Dear Git users,\n\nI hereby announce that Git for Windows 2.37.2 is available from:\n\n    https://gitforwindows.org/\n\nChanges since Git for Windows v2.37.1 (July 12th 2022)\n\n(Upcoming) breaking changes\n\nWe updated the included Bash to version 5.1 (previously 4.4). Please\ncheck your shell scripts for potential compatibility issues.\n\nAlso, as previously announced, Git for Windows dropped support for\nWindows Vista.\n\nAround the beginning of 2023, Git for Windows will drop support for\nWindows 7 and for Windows 8, following Cygwin's and MSYS2's lead (Git\nfor Windows relies on MSYS2 for components such as Bash and Perl).\n\nNew Features\n\n  * Comes with Git v2.37.2.\n  * Comes with tig v2.5.6.\n  * Comes with Bash v5.1 patchlevel 016 .\n  * Comes with Perl v5.36.0.\n  * Git's executables are now marked Terminal Server-aware, meaning:\n    Git will be slightly faster when being run using Remote Desktop\n    Services.\n  * git svn is now based on subversion v1.14.2.\n  * Comes with GNU TLS v3.7.7.\n\nBug Fixes\n\n  * Git for Windows now ships without the zmore and bzmore utilities\n    (which were broken and included only inadvertently).\n  * A regression in the vimdiff mode of git mergetool has been fixed.\n  * With certain network drives, it was reported that some attributes\n    associated with caching confused Git for Windows. This was fixed.\n\nGit-2.37.2-64-bit.exe | 9020623e95e8f250a6298aa98d4bce395adc121998a65bef143556c3fbd2462c\nGit-2.37.2-32-bit.exe | 3f1110d855a934194b8de1e032d8edcb622804a0b4223cccb9379f7d37a52915\nPortableGit-2.37.2-64-bit.7z.exe | 71294d3008d6da6bd25527498ff726d09d55c2cbd1af32d8e99200d5339d7817\nPortableGit-2.37.2-32-bit.7z.exe | 005253af6f96fc86a2ccec97dfd68c56f5b91f72c5cd953e5d1d240c35235390\nMinGit-2.37.2-64-bit.zip | 197422464897cfc8f6ebd73007c798658d21310a4c32d43888c9e8f92720ffec\nMinGit-2.37.2-32-bit.zip | 77b39507cc4b06cad754137e08465c14532b3fc4b0bc4cfc3c91dfeaa6badbe8\nMinGit-2.37.2-busybox-64-bit.zip | bfe43199e74d3d80ed7490b7f0aa09a92f907ecbe9ad80719a9bdf6a8ec4ae70\nMinGit-2.37.2-busybox-32-bit.zip | a752814318a5cc0c00902d5fafffb97c7201ac2e837e0718eaeaddd3fdf3bb07\nGit-2.37.2-64-bit.tar.bz2 | 0508cba06cc52b0e4e733cdd6ee19ad17cc67d31b69c34212f120c94f1806a98\nGit-2.37.2-32-bit.tar.bz2 | f2612e4ff5d63d922673b1c6437b8c292ecdcfd950a2f0bdf4704d6eedc42def\n\nCiao,\nJohannes\n"},{"id":"461103","messageId":"xmqq4jyie9aj.fsf@gitster.g","threadId":"58293","inReplyTo":"20220811214252.4351-1-johannes.schindelin@gmx.de","subject":"Re: [ANNOUNCE] Git for Windows 2.37.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-08-11T21:53:56Z","receivedAt":"2022-08-11T21:54:02Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <johannes.schindelin@gmx.de> writes:\n\n> Dear Git users,\n>\n> I hereby announce that Git for Windows 2.37.2 is available from:\n>\n>     https://gitforwindows.org/\n>\n> Changes since Git for Windows v2.37.1 (July 12th 2022)\n\nThanks.\n"},{"id":"461105","messageId":"0e859fe2-3f23-4526-083c-082adb0028fc@github.com","threadId":"58293","inReplyTo":"20220811214252.4351-1-johannes.schindelin@gmx.de","subject":"Re: [ANNOUNCE] Git for Windows 2.37.2","fromName":"Victoria Dye","fromEmail":"vdye@github.com","sentAt":"2022-08-11T23:22:11Z","receivedAt":"2022-08-11T23:22:17Z","isPatch":false,"sender":{"key":"vdye@github.com","avatar":"https://avatars.githubusercontent.com/u/3619353?v=4"},"body":"Johannes Schindelin wrote:\n> Dear Git users,\n> \n> I hereby announce that Git for Windows 2.37.2 is available from:\n> \n>     https://gitforwindows.org/\nJust a heads-up: there was an issue with the process used to generate this\nversion. Consequently, a large chunk of Git for Windows-specific changes\n(bugfixes, interoperability changes, etc.) is missing from this release. \n\nA fixed release in in progress (see [1] for the latest updates, if you're\ninterested). In the meantime, please *do not* use this version.\n\nThanks,\n- Victoria\n\n[1] https://github.com/git-for-windows/git/pull/3981\n\n> \n> Changes since Git for Windows v2.37.1 (July 12th 2022)\n> \n> (Upcoming) breaking changes\n> \n> We updated the included Bash to version 5.1 (previously 4.4). Please\n> check your shell scripts for potential compatibility issues.\n> \n> Also, as previously announced, Git for Windows dropped support for\n> Windows Vista.\n> \n> Around the beginning of 2023, Git for Windows will drop support for\n> Windows 7 and for Windows 8, following Cygwin's and MSYS2's lead (Git\n> for Windows relies on MSYS2 for components such as Bash and Perl).\n> \n> New Features\n> \n>   * Comes with Git v2.37.2.\n>   * Comes with tig v2.5.6.\n>   * Comes with Bash v5.1 patchlevel 016 .\n>   * Comes with Perl v5.36.0.\n>   * Git's executables are now marked Terminal Server-aware, meaning:\n>     Git will be slightly faster when being run using Remote Desktop\n>     Services.\n>   * git svn is now based on subversion v1.14.2.\n>   * Comes with GNU TLS v3.7.7.\n> \n> Bug Fixes\n> \n>   * Git for Windows now ships without the zmore and bzmore utilities\n>     (which were broken and included only inadvertently).\n>   * A regression in the vimdiff mode of git mergetool has been fixed.\n>   * With certain network drives, it was reported that some attributes\n>     associated with caching confused Git for Windows. This was fixed.\n> \n> Git-2.37.2-64-bit.exe | 9020623e95e8f250a6298aa98d4bce395adc121998a65bef143556c3fbd2462c\n> Git-2.37.2-32-bit.exe | 3f1110d855a934194b8de1e032d8edcb622804a0b4223cccb9379f7d37a52915\n> PortableGit-2.37.2-64-bit.7z.exe | 71294d3008d6da6bd25527498ff726d09d55c2cbd1af32d8e99200d5339d7817\n> PortableGit-2.37.2-32-bit.7z.exe | 005253af6f96fc86a2ccec97dfd68c56f5b91f72c5cd953e5d1d240c35235390\n> MinGit-2.37.2-64-bit.zip | 197422464897cfc8f6ebd73007c798658d21310a4c32d43888c9e8f92720ffec\n> MinGit-2.37.2-32-bit.zip | 77b39507cc4b06cad754137e08465c14532b3fc4b0bc4cfc3c91dfeaa6badbe8\n> MinGit-2.37.2-busybox-64-bit.zip | bfe43199e74d3d80ed7490b7f0aa09a92f907ecbe9ad80719a9bdf6a8ec4ae70\n> MinGit-2.37.2-busybox-32-bit.zip | a752814318a5cc0c00902d5fafffb97c7201ac2e837e0718eaeaddd3fdf3bb07\n> Git-2.37.2-64-bit.tar.bz2 | 0508cba06cc52b0e4e733cdd6ee19ad17cc67d31b69c34212f120c94f1806a98\n> Git-2.37.2-32-bit.tar.bz2 | f2612e4ff5d63d922673b1c6437b8c292ecdcfd950a2f0bdf4704d6eedc42def\n> \n> Ciao,\n> Johannes\n\n"},{"id":"461124","messageId":"xmqqwnbdct1m.fsf@gitster.g","threadId":"58293","inReplyTo":"0e859fe2-3f23-4526-083c-082adb0028fc@github.com","subject":"Re: [ANNOUNCE] Git for Windows 2.37.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-08-12T16:42:29Z","receivedAt":"2022-08-12T16:42:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Victoria Dye <vdye@github.com> writes:\n\n> Johannes Schindelin wrote:\n> Just a heads-up: there was an issue with the process used to generate this\n> version. ...\n\nSorry to see that it caused two cycles of release process.  Would it\nhave helped you if I had done things differently (other than \"not\nissuing maintenance releases that are not security relevant\"), perhaps\ngiving a notice in advance by say a few days?\n\nThanks.\n"},{"id":"461219","messageId":"16r2s842-1r7r-p05n-82o5-q01921r35oqr@tzk.qr","threadId":"58293","inReplyTo":"xmqqwnbdct1m.fsf@gitster.g","subject":"fixup! bug, was Re: [ANNOUNCE] Git for Windows 2.37.2","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-08-15T11:30:20Z","receivedAt":"2022-08-15T11:30:32Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Fri, 12 Aug 2022, Junio C Hamano wrote:\n\n> Victoria Dye <vdye@github.com> writes:\n>\n> > Johannes Schindelin wrote:\n> > Just a heads-up: there was an issue with the process used to generate this\n> > version. ...\n>\n> Sorry to see that it caused two cycles of release process.  Would it\n> have helped you if I had done things differently (other than \"not\n> issuing maintenance releases that are not security relevant\"), perhaps\n> giving a notice in advance by say a few days?\n\nThank you for offering to accommodate Git for Windows' needs.\n\nIn this instance, we tracked the problem down to\nhttps://github.com/gitgitgadget/git/issues/1321: When a rebase has a\n`pick` & `fixup` sequence and the `pick` failed and was skipped, then the\n`fixup` is still trying to amend `HEAD`, which is incorrect.\n\nIn this instance, that wreaked quite the havoc, dropping most of the\nWindows-specific changes due to mistaking the initial fake merge [*1*] for\na real merge.\n\nI offer a more verbose version of this analysis in\nhttps://github.com/git-for-windows/git/pull/3981#issuecomment-1212856115\n\nCiao,\nDscho\n\nFootnote *1*: In Git for Windows, we use the \"merging-rebase\" strategy\nwhere each rebase starts with a fake merge of the previous commit history\n(\"fake\" because it uses `-s ours` to avoid taking any actual content\nchanges). The idea is that the patches will be as clean and ready to\nsubmit to upstream as possible by rebasing them, yet still be able to\nfast-forward. For more details, see\nhttps://github.com/git-for-windows/build-extra/blob/ab941145aeef/shears.sh#L12-L18\n"},{"id":"461247","messageId":"xmqq35dx4hhp.fsf@gitster.g","threadId":"58293","inReplyTo":"16r2s842-1r7r-p05n-82o5-q01921r35oqr@tzk.qr","subject":"Re: fixup! bug, was Re: [ANNOUNCE] Git for Windows 2.37.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-08-15T16:08:18Z","receivedAt":"2022-08-15T16:08:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> Hi Junio,\n>\n> On Fri, 12 Aug 2022, Junio C Hamano wrote:\n>\n>> Victoria Dye <vdye@github.com> writes:\n>>\n>> > Johannes Schindelin wrote:\n>> > Just a heads-up: there was an issue with the process used to generate this\n>> > version. ...\n>>\n>> Sorry to see that it caused two cycles of release process.  Would it\n>> have helped you if I had done things differently (other than \"not\n>> issuing maintenance releases that are not security relevant\"), perhaps\n>> giving a notice in advance by say a few days?\n>\n> Thank you for offering to accommodate Git for Windows' needs.\n>\n> In this instance, we tracked the problem down to ...\n\nWell, I was not asking for postmortem of a particular breakage,\nper-se.  Such a bug is well within the competent hands of GfW\ndeveloper(s).\n\nI was more interested in learning an improved process, e.g. giving\nyou an advance notice of a few days so that you can do a practice\nrun in the not-so-final-but-close-enough tip of the 'maint' branch\nto find out unexpected recent breakage either in the code or in your\ntoolchain before the real release needs to be made in timely\nfashion, would have helped.\n\nThanks.\n"}]}