From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx.groups.io with SMTP id smtpd.web10.3525.1575435857970972232 for ; Tue, 03 Dec 2019 21:04:18 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.88, mailfrom: liming.gao@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2019 21:04:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,276,1571727600"; d="scan'208";a="385607725" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga005.jf.intel.com with ESMTP; 03 Dec 2019 21:04:17 -0800 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 3 Dec 2019 21:04:17 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 3 Dec 2019 21:04:16 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.90]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.222]) with mapi id 14.03.0439.000; Wed, 4 Dec 2019 13:04:14 +0800 From: "Liming Gao" To: "devel@edk2.groups.io" , "Desimone, Nathaniel L" Subject: Re: Public-Service-Announcement: send-email issues with Git 2.22.0+ Thread-Topic: Public-Service-Announcement: send-email issues with Git 2.22.0+ Thread-Index: AdWqWds9URDLS1o3Qn2EICWO9UQWFwABlggg Date: Wed, 4 Dec 2019 05:04:14 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E55BA49@SHSMSX104.ccr.corp.intel.com> References: <02A34F284D1DA44BB705E61F7180EF0AB5C14981@ORSMSX114.amr.corp.intel.com> In-Reply-To: <02A34F284D1DA44BB705E61F7180EF0AB5C14981@ORSMSX114.amr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: liming.gao@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Nate: Thanks for your sharing. I apply this command in my development machine.= = =20 Thanks Liming >-----Original Message----- >From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of >Nate DeSimone >Sent: Wednesday, December 04, 2019 12:31 PM >To: devel@edk2.groups.io >Subject: [edk2-devel] Public-Service-Announcement: send-email issues with >Git 2.22.0+ >Importance: High > >Hi Everyone, > >I have been dealing with a very frustrating issue recently where all of m= y "CR >LF" line endings get erroneously converted into "LF LF" once I send my pa= tch >to the mailing list. I have discovered the root cause for this problem. T= he issue >is the following commit to git itself: > >https://github.com/git/git/commit/5983ddc165221c3ec2a4299b65cfb2ecc1ce7 >765 > >This change is present in git version 2.20.0 or later, per the release no= tes: > >https://github.com/git/git/blob/v2.22.0/Documentation/RelNotes/2.22.0.txt > >With this change, if you leave sendemail.transferEncoding set to the defa= ult >value of "auto", then git will inspect the body of your email. If it find= s a '\r' >character in the message, then it converts the entire message content int= o >Quoted-Printable encoding. It appears that when groups.io converts the QP >encoding back to text format, the '\r' characters somehow become '\n'. To >workaround this make sure to set the following configuration option: > >git config --global sendemail.transferEncoding 8bit > >This will prevent send-email from converting the message into QP encoding= , >allowing the patches to pass through to the mailing list unharmed. Hope t= hat >saves other people a few hours of frustration. > >Regards, >Nate > >