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.web12.9095.1575981412450008451 for ; Tue, 10 Dec 2019 04:36:52 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=dPSvBuP4; 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=1575981411; 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=aU5W+1JdLhEg2zpcIcn2fIpR3sK9r6LxqwjZjWhE7Y8=; b=dPSvBuP4Y6YDqu7rElMIn1/IHmQVSs9RKRboi4Fj4MmHWtSDY4nBmrU4+jQQp+gDqpGZDL m5s3Wom3RYA6E53u6+1zPP50dGB45LC9HFxIss1saQEHOHL8WQBJz2ekl4JnMvrbw9dI/Q fLGkZA4V0HV9JMBxX9He9jTshBdvDzU= 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-298-JXZKVpYLM02Wxwn3rNTN6Q-1; Tue, 10 Dec 2019 07:36:49 -0500 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D8193107ACC5; Tue, 10 Dec 2019 12:36:47 +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 56F5919C69; Tue, 10 Dec 2019 12:36:46 +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: <077c152f-22f8-ce29-ccaa-10874d5e8381@redhat.com> Date: Tue, 10 Dec 2019 13:36:45 +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.84 on 10.5.11.23 X-MC-Unique: JXZKVpYLM02Wxwn3rNTN6Q-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 10:32, Rabeda, Maciej wrote: > 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 able to apply 'push' label to my/other contributor's pull requests to tianocore/edk2. Important detail: at this stage, we are not dealing with github.com pull requests from *others*. Only following use cases are in scope: (1) maintainer submits a PR, or reopen a PR they submitted earlier, for the purposes of a personal CI build (no "push" label) (2) same as (1), except with the "push" label set, for the purposes of an actual fast-forward merge (not just personal CI build); with the topic branch that's subject to the merge consisting purely of patches that have been posted *and reviewed* earlier on the list. (3) same as (1), except with "non-maintainer contributor" replacing "maintainer" A PR, submitted by anyone for the edk2 project on github.com, such that it does not fall in any of the above categories, should be rejected, just like before. Patch submission and review continues on the mailing list. To put differently, you should *only* set the push label on a PR that: - you have submitted / reopened yourself; and - the topic branch subject to the merge consists only of patches that you authored, or applied from others from the list, *and* have been reviewed on the list; and - the topic branch subject to the merge carries all the feedback tags given on the list (such as Tested-by, Acked-by, Reviewed-by). Basically, as a maintainer, you need to: - follow the list, - once there are approved patches for NetworkPkg, pick them up with "git-am" in a local topic branch, - rebase the local topic branch with "git-rebase", so you can apply the R-b / T-b / A-b tags from the list to the commit messages, - push the above topic branch to your own github repo, - submit a PR for the topic branch, - set the "push" label on the PR. "pick up patches from the list" and "pick up feedback tags from the list" are *not* optional. > I assume that the list of people that can apply that label is limited to EDK II Maintainers or is my assumption wrong? Technically, anyone can create a pull request, and my understanding is that anyone can set the "push" label on their pull request. However (AIUI), the mergify bot will reject and close any PR with the "push" label set if the PR was not submitted by a maintainer in the first place. Thanks Laszlo