From: "fengyunhua" <fengyunhua@byosoft.com.cn>
To: "'Feng, Bob C'" <bob.c.feng@intel.com>, <devel@edk2.groups.io>
Cc: "'Liming Gao'" <gaoliming@byosoft.com.cn>,
"'Chen, Christine'" <yuwei.chen@intel.com>
Subject: 回复: [PATCH] BaseTools/Scripts: Check for added newline at end of file
Date: Tue, 15 Dec 2020 15:08:17 +0800 [thread overview]
Message-ID: <000201d6d2b1$10031490$30093db0$@byosoft.com.cn> (raw)
In-Reply-To: <DM6PR11MB407399D8F9AF83C9E3234574C9C60@DM6PR11MB4073.namprd11.prod.outlook.com>
Hi Bob,
I will update this patch.
Thanks,
Yunhua
-----邮件原件-----
发件人: Feng, Bob C <bob.c.feng@intel.com>
发送时间: 2020年12月15日 12:31
收件人: Yunhua Feng <fengyunhua@byosoft.com.cn>; devel@edk2.groups.io
抄送: Liming Gao <gaoliming@byosoft.com.cn>; Chen, Christine
<yuwei.chen@intel.com>
主题: RE: [PATCH] BaseTools/Scripts: Check for added newline at end of file
Hi Yunhua,
I tested this patch. And I found if there are multiple files change in one
patch, your change can only detect the "new blank" error for the last file.
Thanks,
Bob
-----Original Message-----
From: Yunhua Feng <fengyunhua@byosoft.com.cn>
Sent: Monday, December 14, 2020 8:32 AM
To: devel@edk2.groups.io
Cc: Feng, Bob C <bob.c.feng@intel.com>; Liming Gao
<gaoliming@byosoft.com.cn>; Chen, Christine <yuwei.chen@intel.com>
Subject: [PATCH] BaseTools/Scripts: Check for added newline at end of file
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2685
Adding blank lines at end of file is bad enough practice that git complains
about it when importing patches (with git am):
.git/rebase-apply/patch:105: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Signed-off-by: Yunhua Feng <fengyunhua@byosoft.com.cn>
---
BaseTools/Scripts/PatchCheck.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/BaseTools/Scripts/PatchCheck.py b/BaseTools/Scripts/PatchCheck.
py index 68c984ed0e..1859cdc580 100755
--- a/BaseTools/Scripts/PatchCheck.py
+++ b/BaseTools/Scripts/PatchCheck.py
@@ -316,6 +316,8 @@ class GitDiffCheck:
self.new_bin = []
while self.line_num < self.count and self.format_ok:
line_num = self.line_num
+ if line_num == self.count - 1 and self.lines[line_num].strip()
== '+':
+ self.format_error('New blank line at EOF.')
self.run()
assert(self.line_num > line_num)
self.report_message_result()
--
2.27.0.windows.1
prev parent reply other threads:[~2020-12-15 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 0:32 [PATCH] BaseTools/Scripts: Check for added newline at end of file fengyunhua
2020-12-15 4:31 ` Bob Feng
2020-12-15 7:08 ` fengyunhua [this message]
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='000201d6d2b1$10031490$30093db0$@byosoft.com.cn' \
--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