From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web12.1450.1572650559400785581 for ; Fri, 01 Nov 2019 16:22:39 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KdDYSDIr; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1572650558; 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=l31pxQ203BvhZzLk1SaaHM79IKCuIKQ17aQSRIjkyFc=; b=KdDYSDIrcff3lNIvmov7BCAod03owtLpo0s1jpvKKFfw2+bqFGWUVYIK0C2NdRdiDf9F1j kaujl16apqKZ3YjxkQeBF/vcU28LV8Yhh+H0Pw/a/3/HR8Dn6cRzAH7R2b5uTP+vJJfEqr Lpjr400cUznTpkbMdYRnHlUDIgiIR68= 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-219-UxBKUAoIP4Sw0eeT3WQoKQ-1; Fri, 01 Nov 2019 19:22:35 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1ED2E1800D67; Fri, 1 Nov 2019 23:22:33 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-69.ams2.redhat.com [10.36.116.69]) by smtp.corp.redhat.com (Postfix) with ESMTP id 50A8E5D9CD; Fri, 1 Nov 2019 23:22:27 +0000 (UTC) Subject: Re: [edk2-devel] [Patch v3 00/22] Enable Phase 1 of EDK II CI From: "Laszlo Ersek" To: "Kinney, Michael D" , "devel@edk2.groups.io" Cc: Sean Brogan , Bret Barkelew , "Gao, Liming" , "Feng, Bob C" , Andrew Fish , Leif Lindholm , "Wang, Jian J" , "Lu, XiaoyuX" , "Ni, Ray" , "Wu, Hao A" , "Wu, Jiaxin" , "Fu, Siyuan" , "Yao, Jiewen" , "Zhang, Chao B" , "Gao, Zhichao" , "Dong, Eric" References: <20191029195517.20028-1-michael.d.kinney@intel.com> Message-ID: <3e01b213-daae-e831-5d96-5406bb89e17a@redhat.com> Date: Sat, 2 Nov 2019 00:22:26 +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.14 X-MC-Unique: UxBKUAoIP4Sw0eeT3WQoKQ-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/01/19 23:39, Laszlo Ersek wrote: > * When I submitted PR#87, there had been no conflicts; the PR was simply > blocked on the CI tasks. Now, there are conflicts (I assume due to > intervening pushes, while my PR#87 was blocked). It's useful that the > WebUI points out this change in the status of the PR (i.e., "now > conflicting" vs. "no conflicts just waiting for CI"). However, this > status change has not been emailed to me. >=20 > When this occurs to a PR (for example due to an intervening PR that is > merged), what happens to the pre-empted PR? Does it remain suspended > forever? How does the submitter learn about it? Correction: I did get an email stating "PR can not be merged due to conflict. Please rebase and resubmit". I missed it temporarily because it was apparently only sent to: tianocore/edk2-staging and so it got filed into one of my list folders, not in my inbox. I think this is OK after all. Thanks! Laszlo