xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Tiejun Chen <tiejun.chen@intel.com>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.6 released
Date: Thu, 15 Oct 2015 08:02:06 +0000	[thread overview]
Message-ID: <D2451AB0.21C75%lars.kurth@citrix.com> (raw)
In-Reply-To: <561F72B502000078000AB355@prv-mh.provo.novell.com>


Tiejun,

On 15/10/2015 08:32, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 15.10.15 at 02:59, <tiejun.chen@intel.com> 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

      reply	other threads:[~2015-10-15  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 11:16 Xen 4.6 released Wei Liu
2015-10-07 13:04 ` Konrad Rzeszutek Wilk
2015-10-07 17:43   ` Lars Kurth
2015-10-15  0:59 ` Chen, Tiejun
2015-10-15  7:32   ` Jan Beulich
2015-10-15  8:02     ` Lars Kurth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D2451AB0.21C75%lars.kurth@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=tiejun.chen@intel.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).