From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: stephano <stephano.cetola@linux.intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Community Discussion: General Code and Commit message standards
Date: Thu, 18 Oct 2018 14:22:26 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CA4169F3F@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <8dd58f85-3836-4951-3efe-f4c0aef7a1a1@linux.intel.com>
I would like to know when a patch fixes a BZ. Subject/body I have less strong opinion about.
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> stephano
> Sent: Thursday, October 18, 2018 2:13 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Community Discussion: General Code and Commit message
> standards
>
> This discussion was tabled as it will probably be its own meeting rather
> than part of our general discussions this month.
>
> Recently on the list Laszlo and Star agreed that we should be adding the
> CVE to the subject of any patch that fixes a CVE. I will be documenting
> this in the wiki as well as Contributions.txt.
>
> This thread is meant as a chance to begin discussions before we meet to
> formally review the topic. It will give folks a chance to research any
> known pain points or suggested solutions.
>
> Cheers,
> Stephano
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-10-18 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 9:12 Community Discussion: General Code and Commit message standards stephano
2018-10-18 14:22 ` Carsey, Jaben [this message]
2018-10-18 15:49 ` Andrew Fish
2018-10-18 16:43 ` stephano
2018-10-18 17:11 ` Andrew Fish
2018-10-18 17:21 ` stephano
2018-10-18 23:01 ` Kinney, Michael D
2018-10-19 16:21 ` Jeremiah Cox
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=CB6E33457884FA40993F35157061515CA4169F3F@FMSMSX103.amr.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