public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Liming Gao <gaoliming@byosoft.com.cn>,
	Bob Feng <bob.c.feng@intel.com>,
	Yuwei Chen <yuwei.chen@intel.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] BaseTools: Update SetupGit.py to add new 'fp' alias for patch formatting
Date: Tue, 11 Apr 2023 12:06:00 -0600	[thread overview]
Message-ID: <dd65f553-c97e-b78d-0fb0-9c5d0f6f093f@bsdio.com> (raw)
In-Reply-To: <175382D424388526.3578@groups.io>

Could I get some reviews on this please?


-- 

Rebecca Cran



On 4/6/23 7:28 PM, Rebecca Cran wrote:
> To help people format patches with the correct options, add an alias
> named 'fp' to SetupGit.py that runs format-patch with '-M --stat=1000
> --stat-graph-width=20'.
>
> Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
> ---
>   BaseTools/Scripts/SetupGit.py | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/BaseTools/Scripts/SetupGit.py b/BaseTools/Scripts/SetupGit.py
> index 91814199bfb9..5f93124967bf 100644
> --- a/BaseTools/Scripts/SetupGit.py
> +++ b/BaseTools/Scripts/SetupGit.py
> @@ -57,6 +57,8 @@ MIN_GIT_VERSION = (1, 9, 0)
>   
>   # Set of options to be set identically for all repositories
>   OPTIONS = [
> +    {'section': 'alias',       'option': 'fp',
> +     'value': 'format-patch -M --stat=1000 --stat-graph-width=20'},
>       {'section': 'am',          'option': 'keepcr',            'value': True},
>       {'section': 'am',          'option': 'signoff',           'value': True},
>       {'section': 'cherry-pick', 'option': 'signoff',           'value': True},

       reply	other threads:[~2023-04-11 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175382D424388526.3578@groups.io>
2023-04-11 18:06 ` Rebecca Cran [this message]
2023-04-11 20:14   ` [edk2-devel] [PATCH 1/1] BaseTools: Update SetupGit.py to add new 'fp' alias for patch formatting Michael D Kinney

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=dd65f553-c97e-b78d-0fb0-9c5d0f6f093f@bsdio.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