public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <abner.chang@hpe.com>
Cc: "'Dandan Bi'" <dandan.bi@intel.com>,
	"'Wang, Nickle \(HPS SW\)'" <nickle.wang@hpe.com>,
	"'O'Hanley, Peter \(EXL\)'" <peter.ohanley@hpe.com>
Subject: 回复: [edk2-devel] [VFR REST_STYLE PATCH v2 1/1] VfrSpecification: Add REST_STYLE
Date: Thu, 12 Nov 2020 21:35:04 +0800	[thread overview]
Message-ID: <003801d6b8f8$a0d8c7d0$e28a5770$@byosoft.com.cn> (raw)
In-Reply-To: <CS1PR8401MB11449E27C0E0FC5B2FAE97ECFFE70@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM>

Directly push for it. Now, PR is only enabled in Edk2 Repo.

Thanks
Liming
> -----邮件原件-----
> 发件人: bounce+27952+67377+4905953+8761045@groups.io
> <bounce+27952+67377+4905953+8761045@groups.io> 代表 Abner Chang
> 发送时间: 2020年11月12日 15:31
> 收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io
> 抄送: 'Dandan Bi' <dandan.bi@intel.com>; Wang, Nickle (HPS SW)
> <nickle.wang@hpe.com>; O'Hanley, Peter (EXL) <peter.ohanley@hpe.com>
> 主题: Re: [edk2-devel] [VFR REST_STYLE PATCH v2 1/1] VfrSpecification: Add
> REST_STYLE
> 
> Hi Liming, the way to merge this change is create a PR then merge it
directly?
> 
> Abner
> 
> > -----Original Message-----
> > From: gaoliming [mailto:gaoliming@byosoft.com.cn]
> > Sent: Thursday, November 12, 2020 3:13 PM
> > To: devel@edk2.groups.io; Chang, Abner (HPS SW/FW Technologist)
> > <abner.chang@hpe.com>
> > Cc: 'Dandan Bi' <dandan.bi@intel.com>; Wang, Nickle (HPS SW)
> > <nickle.wang@hpe.com>; O'Hanley, Peter (EXL) <peter.ohanley@hpe.com>
> > Subject: 回复: [edk2-devel] [VFR REST_STYLE PATCH v2 1/1]
> VfrSpecification:
> > Add REST_STYLE
> >
> > Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> >
> > > -----邮件原件-----
> > > 发件人: bounce+27952+67207+4905953+8761045@groups.io
> > > <bounce+27952+67207+4905953+8761045@groups.io> 代表 Abner
> Chang
> > > 发送时间: 2020年11月10日 9:46
> > > 收件人: devel@edk2.groups.io
> > > 抄送: abner.chang@hpe.com; Liming Gao <gaoliming@byosoft.com.cn>;
> > Dandan
> > > Bi <dandan.bi@intel.com>; Nickle Wang <nickle.wang@hpe.com>; Peter
> > > O'Hanley <peter.ohanley@hpe.com>
> > > 主题: [edk2-devel] [VFR REST_STYLE PATCH v2 1/1] VfrSpecification: Add
> > > REST_STYLE
> > >
> > > Add REST_STYLE to question flag
> > >
> > > Signed-off-by: Abner Chang <abner.chang@hpe.com>
> > >
> > > Cc: Liming Gao <gaoliming@byosoft.com.cn>
> > > Cc: Dandan Bi <dandan.bi@intel.com>
> > > Cc: Nickle Wang <nickle.wang@hpe.com>
> > > Cc: Peter O'Hanley <peter.ohanley@hpe.com>
> > > ---
> > >  2_vfr_description_in_bnf/210_vfr_general_token_definition.md | 2 ++
> > >  2_vfr_description_in_bnf/211_vfr_form_definition.md          | 2
> ++
> > >  2 files changed, 4 insertions(+)
> > >
> > > diff --git
> > > a/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> > > b/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> > > index 7dc42f0..48057f5 100644
> > > --- a/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> > > +++ b/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> > > @@ -2,6 +2,7 @@
> > >    2.10 VFR General Token Definition
> > >
> > >    Copyright (c) 2007-2017, Intel Corporation. All rights
> > > reserved.<BR>
> > > +  (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>
> > >
> > >    Redistribution and use in source (original document form) and
> > 'compiled'
> > >    forms (converted to PDF, epub, HTML and other formats) with or
> > > without @@ -117,6 +118,7 @@ questionheaderFlagsField ::=
> > >    | "INTERACTIVE"
> > >    | "RESET_REQUIRED"
> > >    | "OPTIONS_ONLY"
> > > +  | "REST_STYLE"
> > >
> > >  vfrStorageVarId ::=
> > >    ( StringIdentifier "[" Number "]" ) diff --git
> > > a/2_vfr_description_in_bnf/211_vfr_form_definition.md
> > > b/2_vfr_description_in_bnf/211_vfr_form_definition.md
> > > index 2e63bdf..238436b 100644
> > > --- a/2_vfr_description_in_bnf/211_vfr_form_definition.md
> > > +++ b/2_vfr_description_in_bnf/211_vfr_form_definition.md
> > > @@ -2,6 +2,7 @@
> > >    2.11 VFR Form Definition
> > >
> > >    Copyright (c) 2007-2017, Intel Corporation. All rights
> > > reserved.<BR>
> > > +  (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>
> > >
> > >    Redistribution and use in source (original document form) and
> > 'compiled'
> > >    forms (converted to PDF, epub, HTML and other formats) with or
> > > without @@ -786,6 +787,7 @@ oneofoptionFlagsField ::=
> > >    | "INTERACTIVE"
> > >    | "RESET_REQUIRED"
> > >    | "DEFAULT"
> > > +  | "REST_STYLE"
> > >  ```
> > >
> > >  #### BEHAVIORS AND RESTRICTIONS
> > > --
> > > 2.21.0.windows.1
> > >
> > >
> > >
> > >
> > >
> >
> >
> 
> 
> 
> 
> 




  reply	other threads:[~2020-11-12 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  1:46 [VFR REST_STYLE PATCH v2 1/1] VfrSpecification: Add REST_STYLE Abner Chang
2020-11-11  0:50 ` 回复: " gaoliming
2020-11-12  7:13 ` 回复: [edk2-devel] " gaoliming
2020-11-12  7:30   ` Abner Chang
2020-11-12 13:35     ` gaoliming [this message]
2020-11-12 13:57       ` Abner Chang
2020-11-12 14:38         ` 回复: " gaoliming
2020-11-12 15:15           ` Abner Chang
2020-11-13  3:12             ` 回复: " gaoliming

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='003801d6b8f8$a0d8c7d0$e28a5770$@byosoft.com.cn' \
    --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