{"thread":{"id":"44416","subject":"[ANNOUNCE] Git for Windows 2.10.2","startedAt":"2016-11-02T20:58:51Z","lastAt":"2016-11-03T16:51:49Z","messageCount":7,"participants":["Johannes Schindelin","Junio C Hamano","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"305317","messageId":"alpine.DEB.2.20.1611022158140.3108@virtualbox","threadId":"44416","inReplyTo":null,"subject":"[ANNOUNCE] Git for Windows 2.10.2","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-11-02T20:58:43Z","receivedAt":"2016-11-02T20:58:51Z","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.10.2 is available from:\n\n\thttps://git-for-windows.github.io/\n\nChanges since Git for Windows v2.10.1(2) (October 13th 2016)\n\nGit for windows v2.10.1(2) was a MinGit-only release (i.e. there was no\nGit for windows installer for that version).\n\nNew Features\n\n • Comes with Git v2.10.2.\n • Comes with Git Credential Manager v1.8.1.\n • Comes with cURL v7.51.0.\n • Git for Windows can now be built easily with Visual C++ 2015.\n • The installer now logs post-install errors more verbosely.\n • A new option asks the installer to skip installation if Git's files\n are in use.\n • A new option asks the installer to quietly skip downgrading Git for\n Windows, without indicating failure.\n • There is now an explicit option for symbolic link support,\n including a link to a more verbose explanation of the issue.\n\nBug Fixes\n\n • when upgrading Git for Windows, SSH agent processes are now\n auto-terminated.\n • When trying to install/upgrade on a Windows version that is no\n longer supported, we now refuse to do so.\n\nFilename | SHA-256\n-------- | -------\nGit-2.10.2-64-bit.exe | 57238ebf86f8b51e32cab44bb91c8060e04774676b77b9fb92f78e7bc7e9a179\nGit-2.10.2-32-bit.exe | 8b15054a4ea2dd5d2be0471a430d8ae7c772b94e1a1048221083a0040011011c\nPortableGit-2.10.2-64-bit.7z.exe | 101314826892480043d5b11989726fc8ee448991eb7b0a1c61aca751161bc15b\nPortableGit-2.10.2-32-bit.7z.exe | edc616817e96a6f15246bb0dd93c97e53d38d3b2a0b7375f26bd0bd082c41a73\nMinGit-2.10.2-64-bit.zip | a10de5d5a8e71e207eff20d833ca56902a0668940e3def5f21d089e4f533ea40\nMinGit-2.10.2-32-bit.zip | 2b191598bcb37565a2b80729ef8d00c03df02b75f6b9d012080c458999f89cc0\nGit-2.10.2-64-bit.tar.bz2 | 7df449ac1813876b5a2e9215d94bca9458c2e0870c65e5b78bd7fc2a448a2a90\nGit-2.10.2-32-bit.tar.bz2 | 3f8d0bebc53fabad863b8fe352a317fde61833efa4750f96656cf95017a621e8\n\nCiao,\nJohannes\n\n-- \nYou received this message because you are subscribed to the Google Groups \"git-for-windows\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to git-for-windows+unsubscribe@googlegroups.com.\nTo post to this group, send email to git-for-windows@googlegroups.com.\nTo view this discussion on the web visit https://groups.google.com/d/msgid/git-for-windows/20161102204358.6856-1-johannes.schindelin%40gmx.de.\nFor more options, visit https://groups.google.com/d/optout."},{"id":"305351","messageId":"alpine.DEB.2.20.1611031554100.3108@virtualbox","threadId":"44416","inReplyTo":"alpine.DEB.2.20.1611022158140.3108@virtualbox","subject":"Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-11-03T15:15:05Z","receivedAt":"2016-11-03T15:15:14Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi all,\n\nOn Wed, 2 Nov 2016, Johannes Schindelin wrote:\n\n> Dear Git users,\n> \n> It is my pleasure to announce that Git for Windows 2.10.2 is available from:\n> \n> \thttps://git-for-windows.github.io/\n> [...]\n\nI originally intended this to be sent out at the same time as the\nannouncement to the Git for Windows mailing list, finally in an automated\nmanner so that I do not have to sit by the keyboard waiting for the\nuploads to finish (every new Git for Windows version is bundled into 9\ndifferent distributables that all want to be uploaded).\n\nBut.\n\nWhen it finally sent out the mail, and I thought everything was alright,\nthinking that I could turn out for the night with a well-deserved drink, I\ngot this from vger.kernel.org:\n\n-- snip --\nSMTP error from remote server for TEXT command, host: vger.kernel.org (209.132.180.67) reason: 550 5.7.1 Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts.\n-- snap --\n\nIs there *anybody* who could give me a clue what this means?\n\nFor the record, I tried to use `git send-email` to send out the\nannouncement for the very first time, and the headers of the mbox file I\nfed to that command read thusly:\n\n-- snip --\nFrom 2.10.2.windows.1 Mon Sep 17 00:00:00 2001\nFrom: Johannes Schindelin \nDate: Wed, 02 Nov 2016 21:43:54 +0100\nTo: git-for-windows@googlegroups.com, git@vger.kernel.org\nSubject: [ANNOUNCE] Git for Windows 2.10.2\nContent-Type: text/plain; charset=UTF-8\nFcc: Sent\n-- snap --\n\nThe only problem I could *possibly* imagine is this UTF-8 bullet character\nused in the enumerations in the mail body:\n\n\t • [...]\n\nFWIW I like that bullet very much, even if it was not my doing, but w3m's\nrendering of the release notes [*1*].\n\nI would really, really, *really* like to keep automating things to make\nthe release engineering of Git for Windows more painless and boring, but\nthis thing, this unhelpful vger error message is blocking me from doing so\nright now.\n\nHelp, anyone?\n\nThanks,\nDscho\n\nFootnote *1*: The release notes are actually written using Markdown:\nhttps://github.com/git-for-windows/build-extra/blob/master/ReleaseNotes.md\nThose release notes are then rendered into HTML when releasing:\nhttps://github.com/git-for-windows/build-extra/blob/4d6097f/installer/release.sh#L86\nThey are also rendered into nice-looking ASCII via HTML by using both\nMarkdown.perl and w3m, for use in the tag message:\nhttps://github.com/git-for-windows/build-extra/blob/4d6097f/please.sh#L1063-L1066\nSame procedure is used again (to allow for very, very last-minute changes,\nsuch as the inclusion of Git Credential Manager v1.8.1 late yesterday,\njust because I still chased a bug introduced during the high-intensity\ninstaller patching bout last Tuesday) when announcing the new version:\nhttps://github.com/git-for-windows/build-extra/blob/4d6097f/please.sh#L1580-L1582"},{"id":"305352","messageId":"xmqqpomcefzy.fsf@gitster.mtv.corp.google.com","threadId":"44416","inReplyTo":"alpine.DEB.2.20.1611031554100.3108@virtualbox","subject":"Re: Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-11-03T15:32:17Z","receivedAt":"2016-11-03T15:32:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> thinking that I could turn out for the night with a well-deserved drink, I\n> got this from vger.kernel.org:\n>\n> -- snip --\n> SMTP error from remote server for TEXT command, host: vger.kernel.org (209.132.180.67) reason: 550 5.7.1 Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts.\n> -- snap --\n>\n> Is there *anybody* who could give me a clue what this means?\n\nHave you tried postmaster (at vger.kernel.org)?\n\n>\n> For the record, I tried to use `git send-email` to send out the\n> announcement for the very first time, and the headers of the mbox file I\n> fed to that command read thusly:\n>\n> -- snip --\n> From 2.10.2.windows.1 Mon Sep 17 00:00:00 2001\n> From: Johannes Schindelin \n> Date: Wed, 02 Nov 2016 21:43:54 +0100\n> To: git-for-windows@googlegroups.com, git@vger.kernel.org\n> Subject: [ANNOUNCE] Git for Windows 2.10.2\n> Content-Type: text/plain; charset=UTF-8\n> Fcc: Sent\n> -- snap --\n>\n> The only problem I could *possibly* imagine is this UTF-8 bullet character\n> used in the enumerations in the mail body:\n>\n> \t • [...]\n\nThe above header you showed says \"Content-type: text/plain;\ncharset=UTF-8\" and I am hoping that this response to you will go out\nwith that labelling back to vger, so we will hopefully see if that\nbullet is the culprit (I doubt it, though). I have no specific\nsuspect at this point yet, other than \"somebody that gets your\nmessage from send-email and passes to vger may be mangling it\".\n\n"},{"id":"305353","messageId":"20161103153453.4aipi5lxkmkt3kco@sigill.intra.peff.net","threadId":"44416","inReplyTo":"alpine.DEB.2.20.1611031554100.3108@virtualbox","subject":"Re: Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-11-03T15:34:53Z","receivedAt":"2016-11-03T15:35:02Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Nov 03, 2016 at 04:15:05PM +0100, Johannes Schindelin wrote:\n\n> When it finally sent out the mail, and I thought everything was alright,\n> thinking that I could turn out for the night with a well-deserved drink, I\n> got this from vger.kernel.org:\n> \n> -- snip --\n> SMTP error from remote server for TEXT command, host: vger.kernel.org (209.132.180.67) reason: 550 5.7.1 Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts.\n> -- snap --\n> \n> Is there *anybody* who could give me a clue what this means?\n\nThat's a new one for me. One guess, though...\n\n> For the record, I tried to use `git send-email` to send out the\n> announcement for the very first time, and the headers of the mbox file I\n> fed to that command read thusly:\n> \n> -- snip --\n> From 2.10.2.windows.1 Mon Sep 17 00:00:00 2001\n> From: Johannes Schindelin \n> Date: Wed, 02 Nov 2016 21:43:54 +0100\n> To: git-for-windows@googlegroups.com, git@vger.kernel.org\n> Subject: [ANNOUNCE] Git for Windows 2.10.2\n> Content-Type: text/plain; charset=UTF-8\n> Fcc: Sent\n> -- snap --\n\nThis is missing a Content-Transfer-Encoding. I think the default is the\ntraditional 7-bit ascii encoding, but your body has characters with the\nhigh-bit set (your UTF-8 bullet).\n\nTry adding:\n\n Content-Transfer-Encoding: 8bit\n\nI haven't seen this before, but I do recall that vger's MTA is very\npicky about this and wants to rewrite transfer-encodings, so it seems\nplausible.\n\n-Peff\n"},{"id":"305354","messageId":"20161103153845.nhquuoko4utecit2@sigill.intra.peff.net","threadId":"44416","inReplyTo":"20161103153453.4aipi5lxkmkt3kco@sigill.intra.peff.net","subject":"Re: Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-11-03T15:38:45Z","receivedAt":"2016-11-03T15:38:51Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:\n\n> This is missing a Content-Transfer-Encoding. I think the default is the\n> traditional 7-bit ascii encoding, but your body has characters with the\n> high-bit set (your UTF-8 bullet).\n> \n> Try adding:\n> \n> Content-Transfer-Encoding: 8bit\n> \n> I haven't seen this before, but I do recall that vger's MTA is very\n> picky about this and wants to rewrite transfer-encodings, so it seems\n> plausible.\n\nTechnically, I think you'd also need a:\n\n MIME-Version: 1.0\n\nheader. That being said, I just peeked at the send-email code and it\nlooks like we try to add in these headers as necessary. It's possible\nthere's a bug, though. What does \"git send-email --dry-run\" say is in\nthe headers it sends out?\n\n-Peff\n"},{"id":"305355","messageId":"20161103155054.24h3byh4fnpf3s6c@sigill.intra.peff.net","threadId":"44416","inReplyTo":"20161103153845.nhquuoko4utecit2@sigill.intra.peff.net","subject":"Re: Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-11-03T15:50:55Z","receivedAt":"2016-11-03T15:51:04Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Nov 03, 2016 at 11:38:45AM -0400, Jeff King wrote:\n\n> On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:\n> \n> > This is missing a Content-Transfer-Encoding. I think the default is the\n> > traditional 7-bit ascii encoding, but your body has characters with the\n> > high-bit set (your UTF-8 bullet).\n> > \n> > Try adding:\n> > \n> > Content-Transfer-Encoding: 8bit\n> > \n> > I haven't seen this before, but I do recall that vger's MTA is very\n> > picky about this and wants to rewrite transfer-encodings, so it seems\n> > plausible.\n> \n> Technically, I think you'd also need a:\n> \n> MIME-Version: 1.0\n> \n> header. That being said, I just peeked at the send-email code and it\n> looks like we try to add in these headers as necessary. It's possible\n> there's a bug, though. What does \"git send-email --dry-run\" say is in\n> the headers it sends out?\n\nAnswering my own question, it looks like send-email gets confused when\nyou give a content-type but no content-transfer-encoding. It wants to\nfill in both or neither.\n\nThis probably helps:\n\ndiff --git a/git-send-email.perl b/git-send-email.perl\nindex da81be40c..784bb874b 100755\n--- a/git-send-email.perl\n+++ b/git-send-email.perl\n@@ -1568,11 +1568,13 @@ foreach my $t (@files) {\n \tpush @cc, recipients_cmd(\"cc-cmd\", \"cc\", $cc_cmd, $t)\n \t\tif defined $cc_cmd && !$suppress_cc{'cccmd'};\n \n-\tif ($broken_encoding{$t} && !$has_content_type) {\n+\tif ($broken_encoding{$t}) {\n \t\t$xfer_encoding = '8bit' if not defined $xfer_encoding;\n-\t\t$has_content_type = 1;\n-\t\tpush @xh, \"Content-Type: text/plain; charset=$auto_8bit_encoding\";\n-\t\t$body_encoding = $auto_8bit_encoding;\n+\t\tif (!$has_content_type) {\n+\t\t $has_content_type = 1;\n+\t\t push @xh, \"Content-Type: text/plain; charset=$auto_8bit_encoding\";\n+\t\t $body_encoding = $auto_8bit_encoding;\n+\t\t}\n \t}\n \n \tif ($broken_encoding{$t} && !is_rfc2047_quoted($subject)) {\n\nbut I think there is more cleanup to handle this case (e.g., it\nauto-guesses utf-8, but it should pull the value from the existing\ncontent-type header).\n\n-Peff\n"},{"id":"305364","messageId":"alpine.DEB.2.20.1611031750590.3108@virtualbox","threadId":"44416","inReplyTo":"20161103153845.nhquuoko4utecit2@sigill.intra.peff.net","subject":"Re: Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-11-03T16:51:20Z","receivedAt":"2016-11-03T16:51:49Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Peff,\n\nOn Thu, 3 Nov 2016, Jeff King wrote:\n\n> On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:\n> \n> > This is missing a Content-Transfer-Encoding. I think the default is the\n> > traditional 7-bit ascii encoding, but your body has characters with the\n> > high-bit set (your UTF-8 bullet).\n> > \n> > Try adding:\n> > \n> > Content-Transfer-Encoding: 8bit\n> > \n> > I haven't seen this before, but I do recall that vger's MTA is very\n> > picky about this and wants to rewrite transfer-encodings, so it seems\n> > plausible.\n> \n> Technically, I think you'd also need a:\n> \n> MIME-Version: 1.0\n> \n> header.\n\nThat seems to have done the trick, thank you so much!\n\nCiao,\nDscho\n"}]}