From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx.groups.io with SMTP id smtpd.web12.7785.1575970392989682260 for ; Tue, 10 Dec 2019 01:33:13 -0800 Authentication-Results: mx.groups.io; dkim=fail reason="body hash did not verify" header.i=@intel.onmicrosoft.com header.s=selector2-intel-onmicrosoft-com header.b=BnCVYW8K; spf=pass (domain: intel.com, ip: 134.134.136.24, mailfrom: maciej.rabeda@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Dec 2019 01:33:01 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,299,1571727600"; d="scan'208";a="413066885" Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by fmsmga005.fm.intel.com with ESMTP; 10 Dec 2019 01:33:01 -0800 Received: from orsmsx156.amr.corp.intel.com (10.22.240.22) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 01:33:01 -0800 Received: from ORSEDG001.ED.cps.intel.com (10.7.248.4) by ORSMSX156.amr.corp.intel.com (10.22.240.22) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 01:33:00 -0800 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.170) by edgegateway.intel.com (134.134.137.100) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 01:33:00 -0800 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U0jifE6MxXhW24gtTe+YTDcF63aQUHsjYYV7gU671UQ0yoDvaP+m6DD68SFDE5VhgbN+f9b4R4K2eLlajfnHMJFcNjyGoTsQyEoYpwZ4D8gKn5mIhTNQ476VFrh/pjn10A9LwXTHyGF6cxTweHLhDDtWewKGBKJqzTnSRSF0Bsq3AHh1p/gBtRu8TG54LSU9H2r1lFXlm08EjjGTaEjg4IjqGLWuniebhnkxzsERa+jz5TYwvfV7scAFqEuwHpxMCQYAh20xSHSi+BJMFNq2i4fcFtjs7bSpsYbRtivF4ERwOHtnrbo0jNSviEY1ObRaWZ9ZkuWYf84I+1V1Q0px3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3x8SVI93HDsIip+HE6l4kBYNKzNJH18NR4ybquKXXIo=; b=ZcfY56RtigHK9WiAgSwCpWXW95nLnH9v+ITxogdpzTBX9VlmXqtn2LjYrvJx//ao0PTPVUk6zi/Ri8JFAuDGcBoVThoNP9AVGecAqryIn06BJoT/27O1KfozVldSG8Ib+t/8RWON9DU4aaOYGKdrEZBnlN4ik/25rWQLOZMN76TQ5YpF4nIWXqSNm27sblLAJFJmMhl1x1eOP9RVfg0hkD+abnIX1otwtOhM+lC0JE/UyFBIP2Xo2vPLSu6QqCICF8jjWiQGcpnNHHnMEl0ai6PEsp367xJQolZe+R/484wsXJSV3NZjaFe+IRTNDE9KfNydfTWMKW9HuJSI3xuRjw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3x8SVI93HDsIip+HE6l4kBYNKzNJH18NR4ybquKXXIo=; b=BnCVYW8KfkSR8P5dwkHNXyYQIMGQNwMvP7bxzm0X+NkxyqsSbEQeLn4NIR4JUOcDQCQi5u289hjvHjsEmoM/GFUZ9t34ErjXKeUF7tj3YrVgH1RccQveOW+Atixd+hmvsRB5T50BMpfeRUmw39RjTCY8oR+MLh6PtqoAoq+imrw= Received: from BYAPR11MB3527.namprd11.prod.outlook.com (20.177.226.90) by BYAPR11MB2790.namprd11.prod.outlook.com (52.135.226.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.22; Tue, 10 Dec 2019 09:32:59 +0000 Received: from BYAPR11MB3527.namprd11.prod.outlook.com ([fe80::710d:6e83:7ce:6f3c]) by BYAPR11MB3527.namprd11.prod.outlook.com ([fe80::710d:6e83:7ce:6f3c%6]) with mapi id 15.20.2516.017; Tue, 10 Dec 2019 09:32:59 +0000 From: "Rabeda, Maciej" To: Laszlo Ersek , "devel@edk2.groups.io" , "Wu, Jiaxin" , Maciej Rabeda , "Kinney, Michael D" , "Gao, Liming" CC: "Fu, Siyuan" Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address Thread-Topic: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address Thread-Index: AQHVrFJuxG2GIZdga0mj8hME+xvvEqey30WAgAAwaYCAAAsbAIAABKog Date: Tue, 10 Dec 2019 09:32:58 +0000 Message-ID: References: <20191206162855.2155-1-maciej.rabeda@linux.intel.com> <895558F6EA4E3B41AC93A00D163B727416FBF2B4@SHSMSX107.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2JjMmViMjUtYzQ0ZS00OGIzLWE2ZmMtNmQwNmJlZDI1MTYyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiNFROV3ZVYkRQMkorU3d0S2tVTk9IYmNBSnZkcGJKU2hLWkk3Y1BFUmIwb1lKOEU0XC9pTUl5Z3pNcEgzMk5ON2gifQ== dlp-reaction: no-action dlp-version: 11.2.0.6 authentication-results: spf=none (sender IP is ) smtp.mailfrom=maciej.rabeda@intel.com; x-originating-ip: [134.191.221.96] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 09c9dc1f-cdf0-4df2-34fa-08d77d53f1e1 x-ms-traffictypediagnostic: BYAPR11MB2790: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 02475B2A01 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(366004)(39860400002)(396003)(376002)(136003)(346002)(189003)(13464003)(199004)(81156014)(8676002)(4326008)(81166006)(66556008)(478600001)(66476007)(8936002)(66946007)(52536014)(76116006)(64756008)(53546011)(6506007)(186003)(33656002)(110136005)(305945005)(9686003)(966005)(7696005)(6636002)(26005)(15650500001)(316002)(2420400007)(71200400001)(7110500001)(18074004)(86362001)(71190400001)(2906002)(229853002)(5660300002)(55016002)(66446008);DIR:OUT;SFP:1102;SCL:1;SRVR:BYAPR11MB2790;H:BYAPR11MB3527.namprd11.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;MX:1;A:1; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: q6m9IIlqI7Ao7T6VijQzlkzTdrAK5Wd0ViCa8rmQPjNF9vdw08NkJ+Y/E5ywc8CbrfLr8U87ZdBEbXp43whHNl6Tgbly7J1qIIyKLIFqzDxqhL71SzAejMgNTcuDyRxsC6BVzKyNWrekycNlLzPFk1jRTXfJmhQaemBg3HnPnzskpKgB39YGilF2rby0D6gUTQQOhMj6muLx1FN3LLN4z6skO8HAyeGFHPOa8NIt9u7MDVkA+aHgxOdjcelMGlRJN1J9Ims17/vYnLxPRQH/0XQcJxgJ76EmKeseeDNjeZ92H2K15IMs3nCGS5/6a1QZUOL66o5Xp3ZI/SGLaWdG1wNylQOlbBBViqQvsR34EXlzvAfDYBNRtGjovdU6qBG+Net3L57wlU+Gj7UXPqi9F0fE8ynp6AY8PH+kbz1ogZDuk0jznL06UtBDdAPRXAKmxGJsw5FiRUueIexUb/Lu0YArPOCIoIGlbojyFZX5qDCBnJwMSSIebQ01iIN+QuDExP6yc9IXAcGJW219otpfv5GBoDI4c7V1ZN86p7wKno0= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 09c9dc1f-cdf0-4df2-34fa-08d77d53f1e1 X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Dec 2019 09:32:58.8841 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: gQss090PdnrzegarOXvdntiXgjWkF/uq8HSfpydH2676gg489GFe354xetvUrWYUm/1eKiZuqAxVXqb0w4LUfw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2790 Return-Path: maciej.rabeda@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Laszlo, Understood, Jiaxin and I have successfully went with one patch via PR flow= already. I was wondering whether any extra actions are required so that I will be a= ble to apply 'push' label to my/other contributor's pull requests to tianoc= ore/edk2. I assume that the list of people that can apply that label is limited to E= DK II Maintainers or is my assumption wrong? Thanks! Maciej -----Original Message----- From: Laszlo Ersek =20 Sent: Tuesday, December 10, 2019 10:11 To: Rabeda, Maciej ; devel@edk2.groups.io; Wu, Ji= axin ; Maciej Rabeda ; = Kinney, Michael D ; Gao, Liming Cc: Fu, Siyuan Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email a= ddress On 12/10/19 09:35, Rabeda, Maciej wrote: > Ok, Jiaxin :) > > Mike, Laszlo, Liming, > > Do you know who I should contact in regards to maintainership role=20 > transition (edk2 write access etc.)? Write access directly to the edk2 repo has been revoked from maintainers. Documentation updates are underway by Mike, to my understanding. Please se= e the following threads: - [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master http://mid.mail-archive.com/E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORS= MSX113.amr.corp.intel.com https://edk2.groups.io/g/devel/message/50407 - [edk2-devel] [Patch wiki v2] EDK II CI: Update Phase 1 details and admin= settings http://mid.mail-archive.com/20191202175630.12788-1-michael.d.kinney@inte= l.com https://edk2.groups.io/g/devel/message/51556 - [edk2-devel] [Patch wiki v2] EDK II Dev Process: Change push to GitHub p= ull request http://mid.mail-archive.com/20191202180131.876-1-michael.d.kinney@intel.= com https://edk2.groups.io/g/devel/message/51557 For a brief (personal, informal) summary, I can offer (quoting an email I = sent earlier): - prepare a local topic branch, on top of master, with the review tags in place, such that (per the earlier method) you'd ff-push that topic branch as the new edk2 master. - instead of pushing it to edk2, push it to your personal edk2 repo on github.com - log in to github.com, and initiate a pull request against edk2/master, from your personal topic branch - as soon as the pull request has been filed, locate the "labels" box to the right, and apply the "push" label. Once the CI tests complete, the branch will be merged (fast-forwarded). The official description will be in the wiki, containing even screenshots.= See the third reference above, from Mike. For now, those updates can be se= en rendered in Mike's clone of the Wiki, namely at . Thanks Laszlo > -----Original Message----- > From: devel@edk2.groups.io On Behalf Of Wu,=20 > Jiaxin > Sent: Tuesday, December 10, 2019 06:38 > To: Maciej Rabeda ;=20 > devel@edk2.groups.io > Cc: Fu, Siyuan > Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer=20 > email address > > Hi Maciej, > > I think now you can update you as one of NetworkPkg maintainers, if so, = you can get the edk2 repo write privilege, which can facility your future c= ontribution. I will still keep the maintainer role until next month. After = that, both Siyuan and I will be reviewer, so, we can still help the technic= al review/support. > > If no objection, just do that:). > > Thanks, > Jiaxin > >> -----Original Message----- >> From: Maciej Rabeda >> Sent: Saturday, December 7, 2019 12:29 AM >> To: devel@edk2.groups.io >> Cc: Wu, Jiaxin ; Fu, Siyuan=20 >> >> Subject: [PATCH] Maintainers.txt: Update reviewer email address >> >> Created new email account that will not append legal disclaimers to=20 >> my responses/patches. >> >> Cc: Jiaxin Wu >> Cc: Siyuan Fu >> Signed-off-by: Maciej Rabeda >> --- >> Maintainers.txt | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/Maintainers.txt b/Maintainers.txt index >> 180ad35d0976..246583204139 100644 >> --- a/Maintainers.txt >> +++ b/Maintainers.txt >> @@ -379,7 +379,7 @@ F: NetworkPkg/ >> W: https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg >> >> M: Jiaxin Wu >> >> R: Siyuan Fu >> >> -R: Maciej Rabeda >> >> +R: Maciej Rabeda >> >> >> >> OvmfPkg >> >> F: OvmfPkg/ >> >> -- >> 2.24.0.windows.2 > > >=20 > > -------------------------------------------------------------------- > > Intel Technology Poland sp. z o.o. > ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII W= ydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52= -316 | Kapital zakladowy 200.000 PLN. > > Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego=20 > adresata i moze zawierac informacje poufne. W razie przypadkowego otrzym= ania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usunie= cie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione. > This e-mail and any attachments may contain confidential material for=20 > the sole use of the intended recipient(s). If you are not the intended r= ecipient, please contact the sender and delete all copies; any review or di= stribution by others is strictly prohibited. > -------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wyd= zial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-3= 16 | Kapital zakladowy 200.000 PLN. Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresat= a i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej w= iadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakie= kolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the = sole use of the intended recipient(s). If you are not the intended recipien= t, please contact the sender and delete all copies; any review or distribut= ion by others is strictly prohibited.