All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <pl@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: RE: New Release Process
Date: Fri, 27 Jan 2006 15:45:31 -0600	[thread overview]
Message-ID: <43DA947B.3050602@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D40A3A3@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
> What do you think? Should we stick with 2.6.15 or go to 2.6.16-rc1 ?
>   
I agree that skipping 2.6.15 and going straight to the 2.6.16 latest rc 
kernels would be a good thing, however I'm confused about one thing (or 
more likely I'm just dense).  Are you looking at pulling in one of the 
alternate kernel hg trees on xenbits, or just manually updating the 
sparse tree to 2.6.16-rc1.  We have the 2.6.16 subarch merge tree, the 
2.6.16 merge tree under ext, and the hvm tree under ext also.  Is one of 
these going to become the new basis for the sparse tree?

Another question this brings up: what is the process for syncing 
relevant changes and fixes between sparse, 2.6 merge, 2.6 subarch, and 
the hvm tree?  Is there any plan to consolidate these?

Thanks,
Paul Larson

  parent reply	other threads:[~2006-01-27 21:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 18:20 New Release Process Ian Pratt
2006-01-26 18:30 ` Mark Williamson
2006-01-26 18:32 ` Nivedita Singhvi
2006-01-26 18:45 ` Matt Ayres
2006-01-27 10:36   ` Keir Fraser
2006-01-27 23:18     ` Matt Ayres
2006-01-26 19:31 ` Anthony Liguori
2006-01-27 10:56 ` Gerd Hoffmann
2006-01-27 15:04   ` Vincent Hanquez
2006-01-27 21:45 ` Paul Larson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-28  8:40 Ian Pratt
2006-01-27 22:10 Ian Pratt
2006-01-27 19:56 Wahlig, Elsie
2006-01-27  3:02 Nakajima, Jun
2006-01-26 23:34 Ian Pratt
2006-01-26 19:42 Nakajima, Jun
2006-01-24 23:11 Ian Pratt
2006-01-24 23:18 ` Matt Ayres
2006-01-25  9:59 ` Patrick Scharrenberg

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=43DA947B.3050602@us.ibm.com \
    --to=pl@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.