From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=stephano.cetola@linux.intel.com; receiver=edk2-devel@lists.01.org Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0C9292194D387 for ; Thu, 18 Oct 2018 09:43:37 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2018 09:43:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,397,1534834800"; d="scan'208";a="89363210" Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.252.17.151]) ([10.252.17.151]) by FMSMGA003.fm.intel.com with ESMTP; 18 Oct 2018 09:43:35 -0700 To: Andrew Fish , "Carsey, Jaben" Cc: "edk2-devel@lists.01.org" References: <8dd58f85-3836-4951-3efe-f4c0aef7a1a1@linux.intel.com> <3ADBB72A-4190-4D58-A359-E493BB1A65CB@apple.com> From: stephano Message-ID: <18984317-b515-9788-0495-af2b0b698ba9@linux.intel.com> Date: Thu, 18 Oct 2018 17:43:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <3ADBB72A-4190-4D58-A359-E493BB1A65CB@apple.com> Subject: Re: Community Discussion: General Code and Commit message standards X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 16:43:38 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit On 10/18/2018 4:49 PM, Andrew Fish wrote: > > >> On Oct 18, 2018, at 7:22 AM, Carsey, Jaben 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