public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Guomin Jiang" <guomin.jiang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-discuss] Best Known Methods for avoiding sending abnormal patch
Date: Tue, 28 Apr 2020 11:30:27 +0000	[thread overview]
Message-ID: <DM6PR11MB29559E6FD2B44E57B29714CD9DAC0@DM6PR11MB2955.namprd11.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]

Hi All,

I encounter a error recently, and it will result in abnormal patch, abnormal CI build and abnormal edk2-devel message.

You can run ``` git config sendemail.transferencoding 8bit``` to avoid the error.

The detail information as below,
When I ready a patch and send it to devel@edk2.groups.io<mailto:devel@edk2.groups.io>, will see below abnormal picture.

>From Mail:
[cid:image001.png@01D61D85.07F968D0]

>From groups.io
[cid:image002.png@01D61D86.BD272250]

>From CI:
[cid:image003.png@01D61D86.BD272250]

The defect happened because of CR+LF is keep in patch and will keep in mail, it seem that the CI or groups system haven't dispose it correctly.

I get the answers from https://stackoverflow.com/questions/6289001/git-am-format-patch-control-format-of-line-endings, and bit8 can avoid unnecessary CR when send email. It explain the history why import the option as well.

https://git-scm.com/docs/git-send-email provide the usage for the option.

Help it is useful for yours

Best Regards
guomin

[-- Attachment #1.2: Type: text/html, Size: 5619 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 107498 bytes --]

[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 68841 bytes --]

[-- Attachment #4: image003.png --]
[-- Type: image/png, Size: 61454 bytes --]

             reply	other threads:[~2020-04-28 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 11:30 Guomin Jiang [this message]
2020-04-29 19:58 ` [edk2-devel] [edk2-discuss] Best Known Methods for avoiding sending abnormal patch Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR11MB29559E6FD2B44E57B29714CD9DAC0@DM6PR11MB2955.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox