xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Steve Johnston <steve.johnston@adventiumlabs.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Submitting a patch for 4.0.1?
Date: Tue, 03 Apr 2012 16:56:05 +0100	[thread overview]
Message-ID: <CBA0DC25.3D52B%keir@xen.org> (raw)
In-Reply-To: <20347.3804.956615.607757@mariner.uk.xensource.com>

On 03/04/2012 15:53, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Steve Johnston writes ("[Xen-devel] Submitting a patch for 4.0.1?"):
>> I have been using Xen 4.0.1 and have created/added a new scheduler that
>> I would like to release into the mainline.
>> 
>> Am I able to submit a patch for an older version of Xen or do I need to
>> port my changes to the current devel project?
> 
> New features of this kind will only be accepted into the mainline
> development series.
> 
> However, it would be worthwhile posting your patches as they are,
> against xen-4.0, so that we can see whether we are likely to accept
> them.  That might save you some wasted effort if it turns out that
> your new code is too hard to get into shape or unsuitable in some way.

Also, mainline is feature frozen for 4.2.0 right now, so you have a while
before we would accept a new scheduler anyhow.

 -- Keir

> Thanks,
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2012-04-03 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 14:25 Submitting a patch for 4.0.1? Steve Johnston
2012-04-03 14:53 ` Ian Jackson
2012-04-03 15:56   ` Keir Fraser [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=CBA0DC25.3D52B%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=steve.johnston@adventiumlabs.com \
    --cc=xen-devel@lists.xensource.com \
    /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).