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.100; helo=mga07.intel.com; envelope-from=liming.gao@intel.com; receiver=edk2-devel@lists.01.org Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (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 179D02119C89C for ; Wed, 12 Dec 2018 05:52:18 -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 orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Dec 2018 05:52:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,344,1539673200"; d="scan'208";a="127265516" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga004.fm.intel.com with ESMTP; 12 Dec 2018 05:52:18 -0800 Received: from fmsmsx118.amr.corp.intel.com (10.18.116.18) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Dec 2018 05:52:18 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx118.amr.corp.intel.com (10.18.116.18) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Dec 2018 05:52:17 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.203]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.201]) with mapi id 14.03.0415.000; Wed, 12 Dec 2018 21:52:15 +0800 From: "Gao, Liming" To: Laszlo Ersek , "edk2-devel@lists.01.org" Thread-Topic: [edk2] [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan Thread-Index: AQHUjKnHMhFJip7uLkOHEBzEJ8pDjKV6TVVwgAAcRACAAMA1oA== Date: Wed, 12 Dec 2018 13:52:15 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E38B98A@SHSMSX104.ccr.corp.intel.com> References: <20181205144918.8112-1-liming.gao@intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E38A5AC@SHSMSX104.ccr.corp.intel.com> <0b2bd66d-95bc-9695-8c10-e73a7f8fe5da@redhat.com> In-Reply-To: <0b2bd66d-95bc-9695-8c10-e73a7f8fe5da@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzkwYWIyNzAtYTFiYy00YzExLWJiY2YtN2RmZjk1YTkwMzZjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiajFGaktEdVFVSnB6QXBLTU1CYlwvRUUxUmNxK3Q2NjNNYm82Rk0xWk5hZUcxWkxzaXZLRDlWWEkrSUM0WlFmTysifQ== dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: [Patch] edk2 Readme.md: Add edk2 release tag and edk2 release plan 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: Wed, 12 Dec 2018 13:52:19 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Laszlo: Sorry for the confuse. I don't find the good name for them. I think your = suggestion is good. I will keep it.=20 Thanks Liming > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of La= szlo Ersek > Sent: Wednesday, December 12, 2018 6:22 PM > To: Gao, Liming ; edk2-devel@lists.01.org > Subject: Re: [edk2] [Patch] edk2 Readme.md: Add edk2 release tag and edk2= release plan >=20 > Hi Liming, >=20 > On 12/12/18 01:41, Gao, Liming wrote: > > Hi, all > > I don't get any comments on this change. So, I will push it this week= . >=20 > sorry that I didn't respond earlier. >=20 > I think the structure of your patch series is confusing. The first patch > is for the edk2 project README file. I saw that soon after you posted > these patches, and I thought someone else should comment on the series. > So I skipped the rest of the series as well. >=20 > However, the second patch in the series (which is not numbered, but I > can see the second patch was sent threaded under the first), is for the > edk2 *wiki*. I think that's extremely confusing, modifying multiple > *repositories* in a single patch email thread. The wiki patch should > have been sent separately. >=20 > Furthermore, the subject shouldn't be >=20 > [edk2] [Patch] edk2 wiki: remove ... >=20 > but >=20 > [edk2] [Patch edk2-wiki] remove ... >=20 > For two reasons: >=20 > - This way reviewers will see at once that the *project* (repo) in > question is the wiki. We always put the repo (e.g. edk2-platforms, > edk2-staging) in the bracketed part. >=20 > - When the patch is finally pushed to the wiki, the subject line of the > commit should not say "edk2 wiki". The commit is made to the wiki repo > anyway, so naming it in the commit message is redundant. >=20 >=20 > Anyway, beyond the above meta-comments, I'm fine with the contents of > the patches themselves. The article at > > preserves the list of features added in the November release. That link > is added to Readme.md in the first patch, and in general, > is a generic feature of > github, for all projects. >=20 > Thanks, > Laszlo > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel