From: "Zhang, Chao B" <chao.b.zhang@intel.com>
To: "Wang, Jian J" <jian.j.wang@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Zhang@ml01.01.org" <Zhang@ml01.01.org>
Subject: Re: [PATCH] Maintainers.txt: remove unexpected unicode BOM
Date: Fri, 8 Mar 2019 08:57:45 +0000 [thread overview]
Message-ID: <FF72C7E4248F3C4E9BDF19D4918E90F24DE7DF92@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20190308085554.5236-1-jian.j.wang@intel.com>
HI Jian:
Tks for the fix.
Reviewed-by: Chao Zhang <chao.b.zhang@intel.com>
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Jian J Wang
Sent: Friday, March 8, 2019 4:56 PM
To: edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>; Yao, Jiewen <jiewen.yao@intel.com>; Zhang, Chao B <chao.b.zhang@intel.com>; Zhang@ml01.01.org
Subject: [edk2] [PATCH] Maintainers.txt: remove unexpected unicode BOM
The BOM was introduced by commit 6c05b958df532345a35b418b05effcf7fd51fc4e
accidentally.
Cc: Yao Jiewen <jiewen.yao@intel.com>
Cc: Zhang, Chao B <chao.b.zhang@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
---
Maintainers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Maintainers.txt b/Maintainers.txt index 08a676b236..61c57587a6 100644
--- a/Maintainers.txt
+++ b/Maintainers.txt
@@ -1,4 +1,4 @@
-EDK II Maintainers
+EDK II Maintainers
==================
This file provides information about the primary maintainers for
--
2.17.1.windows.2
next prev parent reply other threads:[~2019-03-08 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 8:55 [PATCH] Maintainers.txt: remove unexpected unicode BOM Jian J Wang
2019-03-08 8:57 ` Zhang, Chao B [this message]
2019-03-08 9:07 ` Wang, Jian J
2019-03-08 12:32 ` Laszlo Ersek
2019-03-08 12:43 ` Wang, Jian J
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=FF72C7E4248F3C4E9BDF19D4918E90F24DE7DF92@shsmsx102.ccr.corp.intel.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