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.65; helo=mga03.intel.com; envelope-from=bob.c.feng@intel.com; receiver=edk2-devel@lists.01.org Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (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 0974D21959CB2 for ; Wed, 6 Mar 2019 17:11:09 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2019 17:11:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,450,1544515200"; d="scan'208";a="149983098" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga004.fm.intel.com with ESMTP; 06 Mar 2019 17:11:09 -0800 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 6 Mar 2019 17:11:08 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 6 Mar 2019 17:11:08 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.158]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.26]) with mapi id 14.03.0415.000; Thu, 7 Mar 2019 09:11:06 +0800 From: "Feng, Bob C" To: "Kinney, Michael D" , "Gao, Liming" , "edk2-devel@lists.01.org" Thread-Topic: EDK II Specifications for edk2-stable201903 tag Thread-Index: AdTUPE6XxaCQ9Uf7SYOa9FFawr2BcgARAOyQ Date: Thu, 7 Mar 2019 01:11:05 +0000 Message-ID: <08650203BA1BD64D8AD9B6D5D74A85D1600A9FD6@SHSMSX101.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: EDK II Specifications for edk2-stable201903 tag 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, 07 Mar 2019 01:11:10 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mike, Yes. the Revision history need to update. I have sent the spec patches v2 w= hich update the Revision History in README.md and table of content in SUMMA= RY.md for INF/FDF/DSC spec. And I added the BZ in the README.md. Thanks, Bob -----Original Message----- From: Kinney, Michael D=20 Sent: Thursday, March 7, 2019 12:59 AM To: Gao, Liming ; Feng, Bob C ;= edk2-devel@lists.01.org; Kinney, Michael D Subject: EDK II Specifications for edk2-stable201903 tag Hi Liming and Bob, I see several EDK II specification updates. I do not see consistent updates to the Revision History In the README.md wi= th link to the BZ for the document change. Please make sure all revision h= istories are up to date with BZ links, and as each BZ is closed put the lin= ks to commits made in the BZ. This allows anyone reading the documents to = follow the link to the BZ from the Revision History, review the change requ= est and follow the links to the commits in GitHub and the easily view the d= ocument changes. Do you want released versions of these documents to align with the edk2-sta= ble201903 tag? The document release process is documented here: https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore= -Documents-Releasing If so, please enter BZ for each document with the requested release version= number along with the SHA hash of on master the release branch is being re= quested. Thanks, Mike