From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=michael.d.kinney@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 679212116747D for ; Thu, 18 Oct 2018 16:01:18 -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 16:01:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,397,1534834800"; d="scan'208";a="89450100" Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by FMSMGA003.fm.intel.com with ESMTP; 18 Oct 2018 16:01:16 -0700 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.89]) by ORSMSX101.amr.corp.intel.com ([169.254.8.122]) with mapi id 14.03.0319.002; Thu, 18 Oct 2018 16:01:16 -0700 From: "Kinney, Michael D" To: stephano , Andrew Fish , "Kinney, Michael D" CC: "Carsey, Jaben" , "edk2-devel@lists.01.org" Thread-Topic: [edk2] Community Discussion: General Code and Commit message standards Thread-Index: AQHUZsLRmH3GAJVoLUWpLF+YK5Ay1KUlg88AgAAYY4CAAA8MAIAAB7EAgAAC1QD//+lqEA== Date: Thu, 18 Oct 2018 23:01:16 +0000 Message-ID: References: <8dd58f85-3836-4951-3efe-f4c0aef7a1a1@linux.intel.com> <3ADBB72A-4190-4D58-A359-E493BB1A65CB@apple.com> <18984317-b515-9788-0495-af2b0b698ba9@linux.intel.com> <7D30FC28-2AE8-48F9-8942-8D5593E009DA@apple.com> <5bfbdb37-54c4-b8a0-9281-ef56d9327ae9@linux.intel.com> In-Reply-To: <5bfbdb37-54c4-b8a0-9281-ef56d9327ae9@linux.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 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 23:01:18 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I would also hope that most (if not all) patches do have an associated BZ. For either a feature request or a bug fix. Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] > On Behalf Of stephano > Sent: Thursday, October 18, 2018 10:21 AM > To: Andrew Fish > Cc: Carsey, Jaben ; edk2- > devel@lists.01.org > Subject: Re: [edk2] Community Discussion: General Code > and Commit message standards >=20 > On 10/18/2018 6:11 PM, Andrew Fish wrote:> What I've done > in the past on > a branch based github PR flow is have a naming convention > for the > branch. For example eng/PR--. > Then we have a > git hook that looks at the branch name and if it sees a > Bugzilla number > it inserts the Bugzilla reference in the bottom of every > commit message > for that branch. The CI also played tricks with the > branch names and > could update the bug tracker with CI results, and the > process status of > the bug. > Interesting. This will make a good point for coming > discussions. I'll > make a note of it. >=20 > I would hope that most modern workflows have a way to > accomplish this in > some automated way. Seems like a pretty standard ask. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel