From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Kurth Subject: Re: Xen 4.6 released Date: Thu, 15 Oct 2015 08:02:06 +0000 Message-ID: References: <20151007111610.GC13274@zion.uk.xensource.com> <561EFA89.6050403@intel.com> <561F72B502000078000AB355@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZmdUH-0005YG-Q5 for xen-devel@lists.xenproject.org; Thu, 15 Oct 2015 08:02:09 +0000 In-Reply-To: <561F72B502000078000AB355@prv-mh.provo.novell.com> Content-Language: en-US Content-ID: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Tiejun Chen Cc: Ian Jackson , Wei Liu , Ian Campbell , "xen-devel@lists.xenproject.org" List-Id: xen-devel@lists.xenproject.org Tiejun, On 15/10/2015 08:32, "Jan Beulich" wrote: >>>> On 15.10.15 at 02:59, wrote: >> Wei and Ian, >> >> Could we merge these following commits into xen-4.6.1? > >Please don't hijack other threads for backport requests, and please >see ./MAINTAINERS of the respective branch for who to send such >to. I wanted to explain why hijacking threads is bad practice. In this example, you would normally start a new mail along the lines of "Please backport XYZ to ABC" and if somebody needed to check why a specific bug fix was back ported in for example 2 yeaqrs, such a mail will be easier to find. Also of course there is the risk that the right people won't read your mail if you hijack a thread. Regards Lars