From: Matt Ayres <matta@tektonic.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: RE: New Release Process
Date: Fri, 27 Jan 2006 18:18:13 -0500 [thread overview]
Message-ID: <43DAAA35.8070306@tektonic.net> (raw)
In-Reply-To: <2618c79b6f76d8068b52c983b38ce0a4@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 26 Jan 2006, at 18:45, Matt Ayres wrote:
>
>>> Any reason not to call 3.0.1 now? There are a load of bug fixes and
>>> improvements over 3.0.0.
>>
>> I'd say 3.0.1 is required as -unstable has essentially become
>> 3.0-testing over the past few weeks. I'd like to see a tree where
>> -unstable is truly unstable and not the most stable.
>
> Upgrading to 2.6.16-rc will probably make your wish come true. ;-)
>
Current -unstable will become 3.0.1, correct? I am wondering as the
Novell guys' CFQ scheduler is turning out to be very useful and with no
troubles so far. It'd be nice to get this included in 3.0.1.
Thank you,
Matt Ayres
next prev parent reply other threads:[~2006-01-27 23:18 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 [this message]
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
-- 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=43DAAA35.8070306@tektonic.net \
--to=matta@tektonic.net \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.