public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jurriaan <thunder7@xs4all.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6 flavours
Date: Thu, 16 Dec 2004 19:54:54 +0000	[thread overview]
Message-ID: <1103226893.21823.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20041216203740.GA23365@middle.of.nowhere>

On Iau, 2004-12-16 at 20:37, Jurriaan wrote:
> I've understood the 2.6.x-ac kernels started with some ide work, then
> included some serial fixes, and may or may not have other bug fixes.
> >From what I read, they are not as all-including as the 2.4.x-ac kernels
> were. Those I recognize most in the 2.6.x-mm kernels.

2.6.x-mm is more like some of the work the old 2.4-ac did in merging new
stuff (its also worth noting that 2.4-ac ended up more stable than 2.4
at times so -mm might be stable)

The -ac tree is trying to be fairly conservative. When I merge stuff
that is a little less conservative because it has to be done then I've
tried to put a note in the relnotes for that release warning people its
more testing grade.

> Whatever you think best, of course. That may be the release where Alan
> says 'Here's the new, experimental next-generation SATA code. It'll
> probably break every partition you have. Send me bug-reports' :-)

That would be Jeff 8)



  reply	other threads:[~2004-12-16 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 20:13 2.6 flavours Maciej Soltysiak
2004-12-16 20:37 ` Jurriaan
2004-12-16 19:54   ` Alan Cox [this message]
2004-12-17  2:05   ` Con Kolivas

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=1103226893.21823.31.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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