From: Hao Wu <hao.a.wu@intel.com>
To: edk2-devel@lists.01.org
Cc: Hao Wu <hao.a.wu@intel.com>, Liming Gao <liming.gao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: [PATCH 0/2] Some refines to BaseTools/PatchCheck.py
Date: Thu, 8 Jun 2017 15:49:22 +0800 [thread overview]
Message-ID: <20170608074924.12900-1-hao.a.wu@intel.com> (raw)
The following two refinements are made to PatchCheck.py:
a. Resolves misreport of 'Patch format error: diff found after end of
patch', when a patch file contains a binary file change and any other
changes after the binary change.
b. Adds detection of adding new binary files in a patch file or in a
commit.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Hao Wu (2):
BaseTools/PatchCheck.py: Fix misreport for binary changes in patch
BaseTools/PatchCheck.py: Add warning info for new binary files
BaseTools/Scripts/PatchCheck.py | 40 ++++++++++++++++++++++++----------------
1 file changed, 24 insertions(+), 16 deletions(-)
--
2.12.0.windows.1
next reply other threads:[~2017-06-08 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:49 Hao Wu [this message]
2017-06-08 7:49 ` [PATCH 1/2] BaseTools/PatchCheck.py: Fix misreport for binary changes in patch Hao Wu
2017-06-08 7:49 ` [PATCH 2/2] BaseTools/PatchCheck.py: Add warning info for new binary files Hao Wu
2017-06-23 6:35 ` [PATCH 0/2] Some refines to BaseTools/PatchCheck.py Gao, Liming
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=20170608074924.12900-1-hao.a.wu@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