From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch 2/3] BaseTools: Update PatchCheck to handle the two [] as prefix
Date: Tue, 18 Oct 2016 00:53:18 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D4F3AB479@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <147672291414.943.6276903307446370586@jljusten-ivb>
Thanks for the comment, when I push the patch I will do the update.
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Justen, Jordan L
Sent: Tuesday, October 18, 2016 12:49 AM
To: Zhu, Yonghong <yonghong.zhu@intel.com>; edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>
Subject: Re: [Patch 2/3] BaseTools: Update PatchCheck to handle the two [] as prefix
A small (not too important) suggestion for the patch subject might be:
BaseTools/PatchCheck.py: Update to handle the two [] as prefix
On 2016-10-17 01:28:37, Yonghong Zhu wrote:
> The bug is that only remove the first [] when it does the char count,
> however sometimes we use [edk2][patch] as prefix, this patch fix this bug.
>
> Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=113
>
Remove blank line after 'Fixes:'.
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> ---
> BaseTools/Scripts/PatchCheck.py | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/BaseTools/Scripts/PatchCheck.py
> b/BaseTools/Scripts/PatchCheck.py index 07fca68..05f8f6e 100755
> --- a/BaseTools/Scripts/PatchCheck.py
> +++ b/BaseTools/Scripts/PatchCheck.py
> @@ -434,10 +434,18 @@ class CheckOnePatch:
> [\s\S\r\n]+
> )
> ''',
> re.IGNORECASE | re.VERBOSE | re.MULTILINE)
>
> + subject_prefix_re = \
> + re.compile(r'''^
> + \s* (\[
> + [^\[\]]* # Allow all non-brackets
> + \])* \s*
> + ''',
> + re.VERBOSE)
> +
> def find_patch_pieces(self):
> if sys.version_info < (3, 0):
> patch = self.patch.encode('ascii', 'ignore')
> else:
> patch = self.patch
> @@ -470,18 +478,11 @@ class CheckOnePatch:
> self.stat = mo.group('stat')
> self.commit_msg = mo.group('commit_message')
>
> self.commit_subject = pmail['subject'].replace('\r\n', '')
> self.commit_subject = self.commit_subject.replace('\n', '')
> -
> - pfx_start = self.commit_subject.find('[')
> - if pfx_start >= 0:
> - pfx_end = self.commit_subject.find(']')
> - if pfx_end > pfx_start:
> - self.commit_prefix = self.commit_subject[pfx_start + 1 : pfx_end]
Since we no longer set self.commit_prefix, and you remove the other references to it in the script?
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
> - self.commit_subject = self.commit_subject[pfx_end + 1 :].lstrip()
> -
> + self.commit_subject = self.subject_prefix_re.sub('',
> + self.commit_subject, 1)
>
> class CheckGitCommits:
> """Reads patches from git based on the specified git revision range.
>
> The patches are read from git, and then checked.
> --
> 2.6.1.windows.1
>
next prev parent reply other threads:[~2016-10-18 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 8:28 [Patch 0/3] BaseTools: PatchCheck to align with wiki and report error for EFI_D_* Yonghong Zhu
2016-10-17 8:28 ` [Patch 1/3] BaseTools: Update PatchCheck for max length of subject and message line Yonghong Zhu
2016-10-17 16:40 ` Jordan Justen
2016-10-18 0:49 ` Zhu, Yonghong
2016-10-17 8:28 ` [Patch 2/3] BaseTools: Update PatchCheck to handle the two [] as prefix Yonghong Zhu
2016-10-17 16:48 ` Jordan Justen
2016-10-18 0:53 ` Zhu, Yonghong [this message]
2016-10-17 8:28 ` [Patch 3/3] BaseTools: Update PatchCheck to report error for EFI_D_* Yonghong Zhu
2016-10-17 16:58 ` Jordan Justen
2016-10-18 2:02 ` Zhu, Yonghong
2016-10-18 6:43 ` Jordan Justen
2016-10-18 10:22 ` 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=B9726D6DCCFB8B4CA276A9169B02216D4F3AB479@SHSMSX103.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