public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bob Feng" <bob.c.feng@intel.com>
To: "Zhang, Shenglei" <shenglei.zhang@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH] BaseTools/PatchCheck.py: Skip length check for user name in xxx-by
Date: Tue, 21 Jul 2020 05:58:04 +0000	[thread overview]
Message-ID: <BN6PR11MB00684FB34B99AE41BB5EADACC9780@BN6PR11MB0068.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BL0PR11MB3506949B9CC0F9B7E52293878C780@BL0PR11MB3506.namprd11.prod.outlook.com>

Shenglei,

I mean this link https://edk2.groups.io/g/devel/message/62647 

Thanks,
Bob

-----Original Message-----
From: Zhang, Shenglei <shenglei.zhang@intel.com> 
Sent: Tuesday, July 21, 2020 1:21 PM
To: Feng, Bob C <bob.c.feng@intel.com>; devel@edk2.groups.io
Cc: Gao, Liming <liming.gao@intel.com>
Subject: RE: [PATCH] BaseTools/PatchCheck.py: Skip length check for user name in xxx-by

Bob,

Code review is for our internal use. Should I append it on Bugzilla?

Thanks,
Shenglei

> -----Original Message-----
> From: Feng, Bob C <bob.c.feng@intel.com>
> Sent: Tuesday, July 21, 2020 11:39 AM
> To: Zhang, Shenglei <shenglei.zhang@intel.com>; devel@edk2.groups.io
> Cc: Gao, Liming <liming.gao@intel.com>
> Subject: RE: [PATCH] BaseTools/PatchCheck.py: Skip length check for 
> user name in xxx-by
> 
> Shenglei,
> 
> After you send out the patch for review, please update the Bugzilla 
> status as in-progress and provide the code review link.
> 
> Thanks,
> Bob
> 
> -----Original Message-----
> From: Zhang, Shenglei <shenglei.zhang@intel.com>
> Sent: Thursday, July 16, 2020 11:14 AM
> To: devel@edk2.groups.io
> Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming 
> <liming.gao@intel.com>
> Subject: [PATCH] BaseTools/PatchCheck.py: Skip length check for user 
> name in xxx-by
> 
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2836
> Current PatchCheck.py checks each line to ensure line's length is not 
> larger than 76. But there's a case that length of user's name is much 
> longer than that number. So enhance the script to handle this case.
> 
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
> ---
>  BaseTools/Scripts/PatchCheck.py | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/BaseTools/Scripts/PatchCheck.py 
> b/BaseTools/Scripts/PatchCheck.py index 52244b0bc4d8..7db0775d14d1
> 100755
> --- a/BaseTools/Scripts/PatchCheck.py
> +++ b/BaseTools/Scripts/PatchCheck.py
> @@ -268,7 +268,14 @@ class CommitMessageCheck:
>          for i in range(2, count):
>              if (len(lines[i]) >= 76 and
>                  len(lines[i].split()) > 1 and
> -                not lines[i].startswith('git-svn-id:')):
> +                not lines[i].startswith('git-svn-id:') and
> +                not lines[i].startswith('Reviewed-by') and
> +                not lines[i].startswith('Acked-by:') and
> +                not lines[i].startswith('Tested-by:') and
> +                not lines[i].startswith('Reported-by:') and
> +                not lines[i].startswith('Suggested-by:') and
> +                not lines[i].startswith('Signed-off-by:') and
> +                not lines[i].startswith('Cc:')):
>                  #
>                  # Print a warning if body line is longer than 75 characters
>                  #
> --
> 2.18.0.windows.1


      reply	other threads:[~2020-07-21  5:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  3:13 [PATCH] BaseTools/PatchCheck.py: Skip length check for user name in xxx-by Zhang, Shenglei
2020-07-16  7:19 ` Liming Gao
2020-07-16  8:26 ` [edk2-devel] " Yuwei Chen
2020-07-21  3:35 ` Bob Feng
2020-07-21  3:38 ` Bob Feng
2020-07-21  5:20   ` Zhang, Shenglei
2020-07-21  5:58     ` 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=BN6PR11MB00684FB34B99AE41BB5EADACC9780@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