All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: make xen/stable-2.6.32.x pvops branch the default?
Date: Tue, 08 Jun 2010 13:19:21 +0200	[thread overview]
Message-ID: <4C0E2739.3040105@redhat.com> (raw)
In-Reply-To: <20100608111501.GP17817@reaktio.net>

On 06/08/2010 01:15 PM, Pasi Kärkkäinen wrote:
> Hello,
>
> Should we switch xen/stable-2.6.32.x to be the default branch in xen-unstable?
> And possibly in xen-4.0-testing.hg aswell?
>
> That's the long-term maintained and the branch most people are using anyway..
>
> -- Pasi
>    

Hi Pasi,
I'm using the default branch which is stable-2.6.31.x now but if the 
long-term maintained one would be the .32.x one I think it's better to 
have it as default since sooner or later I'll have to recompile the 
.32.x version since .31.x won't be maintained so make it a default for 
at least xen-4.1-unstable and newer versions of xen-unstable could be a 
good idea not to force other to clone/pull and recompile the another 
branch than the default one.

Thanks,
Michal
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    


-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

  reply	other threads:[~2010-06-08 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 11:15 make xen/stable-2.6.32.x pvops branch the default? Pasi Kärkkäinen
2010-06-08 11:19 ` Michal Novotny [this message]
2010-06-08 15:49 ` Jeremy Fitzhardinge
2010-06-08 16:15   ` Konrad Rzeszutek Wilk
2010-06-08 16:38     ` Jeremy Fitzhardinge

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=4C0E2739.3040105@redhat.com \
    --to=minovotn@redhat.com \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=pasik@iki.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.