From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.61]) by mx.groups.io with SMTP id smtpd.web09.7547.1575969068228080909 for ; Tue, 10 Dec 2019 01:11:08 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=F8LDOH7X; spf=pass (domain: redhat.com, ip: 205.139.110.61, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575969067; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oV8ZyBIT3T2CkPCVRnslvz+5/5iivh9yi804RIFSILU=; b=F8LDOH7X/7l1uoyUtnGahPZW0EMP4i1jbgS6oB1UNSzaPosH35hu5+5u6RnfutiBIxKgYV 2UD25iAPdCoXU4gRjOwvi+Aca75LaWttFEAZTfuWrp1c7pCLZ5+FvX7jnTjw7oNBZ8wstV xpQurbPjMvW4qG2T2E5SM1huBG/mRH8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-24-CJgjkvOTOASGZd43EeTB5Q-1; Tue, 10 Dec 2019 04:10:54 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EF8E71005512; Tue, 10 Dec 2019 09:10:52 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-225.ams2.redhat.com [10.36.116.225]) by smtp.corp.redhat.com (Postfix) with ESMTP id 37FD65D6D4; Tue, 10 Dec 2019 09:10:51 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address To: "Rabeda, Maciej" , "devel@edk2.groups.io" , "Wu, Jiaxin" , Maciej Rabeda , "Kinney, Michael D" , "Gao, Liming" Cc: "Fu, Siyuan" References: <20191206162855.2155-1-maciej.rabeda@linux.intel.com> <895558F6EA4E3B41AC93A00D163B727416FBF2B4@SHSMSX107.ccr.corp.intel.com> From: "Laszlo Ersek" Message-ID: Date: Tue, 10 Dec 2019 10:10:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: CJgjkvOTOASGZd43EeTB5Q-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 > 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 see the following threads: - [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master http://mid.mail-archive.com/E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORSMSX113.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@intel.com https://edk2.groups.io/g/devel/message/51556 - [edk2-devel] [Patch wiki v2] EDK II Dev Process: Change push to GitHub pull 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 seen rendered in Mike's clone of the Wiki, namely at . Thanks Laszlo > -----Original Message----- > From: devel@edk2.groups.io On Behalf Of Wu, Jiaxin > Sent: Tuesday, December 10, 2019 06:38 > To: Maciej Rabeda ; devel@edk2.groups.io > Cc: Fu, Siyuan > Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer 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 contribution. 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 technical 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 >> Subject: [PATCH] Maintainers.txt: Update reviewer email address >> >> Created new email account that will not append legal disclaimers to 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 > > > > > -------------------------------------------------------------------- > > Intel Technology Poland sp. z o.o. > ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial 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 adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek > 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 recipient, please contact the sender and delete all copies; any review or distribution by > others is strictly prohibited. >