From: stephano <stephano.cetola@linux.intel.com>
To: Andrew Fish <afish@apple.com>, "Carsey, Jaben" <jaben.carsey@intel.com>
Cc: "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 17:43:34 +0100 [thread overview]
Message-ID: <18984317-b515-9788-0495-af2b0b698ba9@linux.intel.com> (raw)
In-Reply-To: <3ADBB72A-4190-4D58-A359-E493BB1A65CB@apple.com>
On 10/18/2018 4:49 PM, Andrew Fish wrote:
>
>
>> On Oct 18, 2018, at 7:22 AM, Carsey, Jaben <jaben.carsey@intel.com> wrote:
>>
>> I would like to know when a patch fixes a BZ. Subject/body I have less strong opinion about.
>>
>
> +1
>
> Thanks,
>
> Andrew Fish
This is always a point of contention with mailing list style
patch-workflows in my experience. I know some groups have had success
with patchwork, but I am hoping whatever workflow we choose will support
this idea.
I'll add this to our list of features for our upcoming discussions.
Thanks guys!
--S
next prev parent reply other threads:[~2018-10-18 16:43 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
2018-10-18 15:49 ` Andrew Fish
2018-10-18 16:43 ` stephano [this message]
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=18984317-b515-9788-0495-af2b0b698ba9@linux.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