From mboxrd@z Thu Jan  1 00:00:00 1970
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by groups.io with SMTP; Mon, 03 Jun 2019 02:29:30 -0700
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 mx1.redhat.com (Postfix) with ESMTPS id 2DE292F8BC8;
	Mon,  3 Jun 2019 09:29:30 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-121-13.rdu2.redhat.com [10.10.121.13])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 9AC982DE69;
	Mon,  3 Jun 2019 09:29:28 +0000 (UTC)
Subject: Re: [edk2-devel] [PATCH v2 00/10] Duplicate required CSM components for OVMF
To: "Wu, Hao A" <hao.a.wu@intel.com>,
 "devel@edk2.groups.io" <devel@edk2.groups.io>,
 David Woodhouse <dwmw2@infradead.org>
Cc: "Ni, Ray" <ray.ni@intel.com>, "Justen, Jordan L"
 <jordan.l.justen@intel.com>, Ard Biesheuvel <ard.biesheuvel@linaro.org>
References: <20190527030350.11996-1-hao.a.wu@intel.com>
 <5bb0b7dc-a16e-3ff9-af6e-3c87c6e3744c@redhat.com>
 <B80AF82E9BFB8E4FBD8C89DA810C6A093C8D72EC@SHSMSX104.ccr.corp.intel.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <f1d688ec-e6cf-5ac9-0fe1-f8790bc25ba2@redhat.com>
Date: Mon, 3 Jun 2019 11:29:27 +0200
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: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8D72EC@SHSMSX104.ccr.corp.intel.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 03 Jun 2019 09:29:30 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 05/29/19 03:12, Wu, Hao A wrote:

> Also, do you expect such BZ dependencies setup should be done by the
> submitters (if they are aware of such dependencies) when they files a BZ
> tracker?

It's best to capture the BZ dependencies as soon as someone realizes
that such dependencies exist. If the submitter can already determine the
deps, they are most welcome to set them immediately. Otherwise, whoever
triages the bugs, or the affected package maintainers, or just someone
reading the bugs list, can do it.

Thanks,
Laszlo