public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"abner.chang@amd.com" <abner.chang@amd.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-CCodingStandardsSpecification] Create release/2.30 branch
Date: Fri, 28 Oct 2022 15:22:17 +0000	[thread overview]
Message-ID: <CO1PR11MB4929AD2AF3756655B9BEDB1ED2329@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221027165416.1610-1-abner.chang@amd.com>

Hi Abner,

Have you reviewed the open BZs against the EDK II C Coding Standard.

Are there any other issues that are considered important to fix before
making a new official release?

Thanks,

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Chang, Abner via groups.io
> Sent: Thursday, October 27, 2022 9:54 AM
> To: devel@edk2.groups.io
> Cc: Abner Chang <abner.chang@amd.com>
> Subject: [edk2-devel] [edk2-CCodingStandardsSpecification] Create release/2.30 branch
> 
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Abner Chang <abner.chang@amd.com>
> ---
>  book.json | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/book.json b/book.json
> index d112b26..1fdd570 100644
> --- a/book.json
> +++ b/book.json
> @@ -1,8 +1,7 @@
>  {
> 
>    "variables" : {
> 
> -    "draft"   : "yes",
> 
>      "title"   : "EDK II C Coding Standards Specification",
> 
> -    "version" : "Revision 2.2"
> 
> +    "version" : "Revision 2.3"
> 
>    },
> 
>    "plugins": ["puml-aleung"],
> 
>    "pluginsConfig": {}
> 
> --
> 2.37.1.windows.1
> 
> 
> 
> 
> 


  reply	other threads:[~2022-10-28 15:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 16:54 [edk2-CCodingStandardsSpecification] Create release/2.30 branch Chang, Abner
2022-10-28 15:22 ` Michael D Kinney [this message]
2022-10-29  3:33   ` [edk2-devel] " Chang, Abner
2022-11-07 14:18     ` Chang, Abner
2022-11-07 17:07       ` Michael D Kinney
2022-11-13  1:37         ` Chang, Abner
2022-11-13  2:01           ` Michael D Kinney
2022-11-13  8:53             ` Chang, Abner
2022-11-13 17:33               ` 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=CO1PR11MB4929AD2AF3756655B9BEDB1ED2329@CO1PR11MB4929.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