From: Jaben Carsey <jaben.carsey@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH v1 0/5] BaseTools: improve reuse and remove dead code
Date: Thu, 15 Mar 2018 14:39:03 -0700 [thread overview]
Message-ID: <cover.1521149858.git.jaben.carsey@intel.com> (raw)
remove class and function definitions that are never used
re-use existing regular expressions instead of compiling
use string format instead of eval()
Jaben Carsey (5):
BaseTools: StrGather has redundant declaration
BaseTools: StrGather simplify string/int conversion functions
BaseTools: StrGather remove functions no one calls
BaseTools: FdfParser & FdfParserLite refactor regular expression for
GUIDs
BaseTools: FdfParser remove class never used.
BaseTools/Source/Python/AutoGen/StrGather.py | 57 +++-----------------
BaseTools/Source/Python/Common/FdfParserLite.py | 4 +-
BaseTools/Source/Python/GenFds/FdfParser.py | 19 +------
3 files changed, 10 insertions(+), 70 deletions(-)
--
2.16.2.windows.1
next reply other threads:[~2018-03-15 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 21:39 Jaben Carsey [this message]
2018-03-15 21:39 ` [PATCH v1 1/5] BaseTools: StrGather has redundant declaration Jaben Carsey
2018-03-15 21:39 ` [PATCH v1 2/5] BaseTools: StrGather simplify string/int conversion functions Jaben Carsey
2018-03-15 21:39 ` [PATCH v1 3/5] BaseTools: StrGather remove functions no one calls Jaben Carsey
2018-03-15 21:39 ` [PATCH v1 4/5] BaseTools: FdfParser & FdfParserLite refactor regular expression for GUIDs Jaben Carsey
2018-03-15 21:39 ` [PATCH v1 5/5] BaseTools: FdfParser remove class never used Jaben Carsey
2018-03-20 8:26 ` [PATCH v1 0/5] BaseTools: improve reuse and remove dead code Zhu, Yonghong
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=cover.1521149858.git.jaben.carsey@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