public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bob Feng" <bob.c.feng@intel.com>
To: Leif Lindholm <leif@nuviainc.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH 0/2] BaseTools: minor PatchCheck.py fixes/changes
Date: Fri, 3 Jul 2020 07:20:14 +0000	[thread overview]
Message-ID: <BN6PR11MB006870DD40CF426369ABBB0DC96A0@BN6PR11MB0068.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200702153934.25262-1-leif@nuviainc.com>

Merged.

-----Original Message-----
From: Leif Lindholm <leif@nuviainc.com> 
Sent: Thursday, July 2, 2020 11:40 PM
To: devel@edk2.groups.io
Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: [PATCH 0/2] BaseTools: minor PatchCheck.py fixes/changes

1: https://github.com/tianocore/edk2/pull/549 failed to merge, since
   PatchCheck.py reports an error. Add BaseTools/Conf/diff.order to
   the same exception clause currently used for .gitmodules to permit
   the merge to progress.

2: On Debian 10, PatchCheck.py fails to run with the system default
   python (2). This patch fixes that.
   (This uses the improved version suggested by Bob.)

Leif Lindholm (2):
  BaseTools/PatchCheck.py: add exception for diff orderfile
  BaseTools: explicitly import email.header PatchCheck.py

Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <liming.gao@intel.com>

 BaseTools/Scripts/PatchCheck.py | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

-- 
2.20.1

      parent reply	other threads:[~2020-07-03  7:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 15:39 [PATCH 0/2] BaseTools: minor PatchCheck.py fixes/changes Leif Lindholm
2020-07-02 15:39 ` [PATCH 1/2] BaseTools/PatchCheck.py: add exception for diff orderfile Leif Lindholm
2020-07-02 23:47   ` [edk2-devel] " Bob Feng
2020-07-02 15:39 ` [PATCH 2/2] BaseTools: explicitly import email.header PatchCheck.py Leif Lindholm
2020-07-02 15:48   ` [edk2-devel] " Bob Feng
2020-07-03  7:20 ` Bob Feng [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=BN6PR11MB006870DD40CF426369ABBB0DC96A0@BN6PR11MB0068.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