From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH v2] qemu-xen:Correctly expose PCH ISA bridge for IGD passthrough [and 2 more messages] Date: Fri, 10 May 2013 11:35:20 +0100 Message-ID: <518CE98802000078000D5150@nat28.tlf.novell.com> References: <20775.45924.670290.551847@mariner.uk.xensource.com> <512B46A402000078000C0B3B@nat28.tlf.novell.com> <20779.18914.422564.346844@mariner.uk.xensource.com> <512B591702000078000C0BCE@nat28.tlf.novell.com> <20873.13822.177086.581233@mariner.uk.xensource.com> <20130509131706.GJ11427@reaktio.net> <518CD61F02000078000D5085@nat28.tlf.novell.com> <20130510094036.GS11427@reaktio.net> <1368180027.27857.56.camel@zakaz.uk.xensource.com> <518CC758.10002@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <518CC758.10002@eu.citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Campbell , StefanoStabellini , Ian Jackson , "G.R." , xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 10.05.13 at 12:09, George Dunlap wrote: > But if he were going to pick it up, or if he wants to go work with the > submitter, who may not have a clear understanding what the delay was > about or how the development process works, then he'd first need to > figure out what the status was, right? But that's what is available in the list archives - in the case at hand, Pasi pointed at patches that had trees of subsequent communication attached to them, and in all cases the leaves where unanswered questions. So figuring out the status was quite strait forward here. I admit that this may not always be as simple (or otherwise I likely wouldn't even have bothered looking at the old conversation again). Bottom line is that I think we should be allowed to expect homework to be done before pinging maintainers. Jan