From: "Ramón Rey Vicente" <retes_simbad@yahoo.es>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "J.A. Magallon" <jamagallon@able.es>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.22 released
Date: Tue, 26 Aug 2003 02:21:34 +0200 [thread overview]
Message-ID: <1061857293.15168.3.camel@debian> (raw)
In-Reply-To: <20030825222215.GX7038@fs.tum.de>
El mar, 26-08-2003 a las 00:22, Adrian Bunk escribió:
> > > > What are the plans for 2.4.23? XFS merge perhaps <hint>?
> > >
> > > ALSA? low latency and related stuff?
> >
> > I think ALSA is interesting to ease the migration to 2.6.
> > Let people move from OSS to ALSA, and then switch from 2.4 to 2.6...
>
> Where's the problem with letting people switch from 2.4 to 2.6 and later
> from OSS to ALSA?
>
> Since OSS is still present in 2.6 I don't see any migration problems.
I think merging ALSA in 2.4 series bring some of the advantages of the
2.6 series to the stable kernel, just new drivers with improvements over
OSS... but I dont think that will help in the switching to 2.6.
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
------------------------------------------------------------
gpg public key ID 0xBEBD71D5 # http://pgp.escomposlinux.org/
next prev parent reply other threads:[~2003-08-26 0:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 11:48 linux-2.4.22 released Marcelo Tosatti
2003-08-25 8:11 ` Enrico Demarin
2003-08-25 13:23 ` Matthias Andree
2003-08-25 13:32 ` Christoph Hellwig
2003-08-25 13:35 ` Ramón Rey Vicente
2003-08-25 21:13 ` J.A. Magallon
2003-08-25 22:22 ` Adrian Bunk
2003-08-26 0:21 ` Ramón Rey Vicente [this message]
2003-08-26 21:49 ` Diego Calleja García
2003-08-26 21:55 ` Adrian Bunk
2003-08-26 22:29 ` Diego Calleja García
2003-08-27 2:15 ` Ramón Rey Vicente
2003-08-27 5:21 ` Gerardo Exequiel Pozzi
2003-08-27 1:20 ` Chuck Campbell
2003-08-27 1:48 ` David van Hoose
2003-08-27 1:55 ` David van Hoose
2003-08-27 3:28 ` Kurt Wall
2003-08-27 2:01 ` Ramón Rey Vicente
2003-08-27 4:12 ` Willy Tarreau
2003-08-26 22:29 ` Matthias Andree
2003-08-27 9:47 ` Bas Mevissen
2003-08-26 13:55 ` Matthias Andree
2003-08-25 13:38 ` Nick Piggin
2003-08-25 22:34 ` Bill Davidsen
2003-08-25 14:38 ` Yann Droneaud
2003-08-25 15:35 ` Krzysztof Halasa
2003-08-25 16:03 ` Luca Montecchiani
2003-08-25 19:18 ` Erik Andersen
2003-08-25 20:00 ` Edesio Costa e Silva
2003-08-25 20:10 ` Tom Rini
2003-08-26 13:19 ` Rene Rebe
2003-08-26 15:00 ` Alan Cox
2003-08-27 3:47 ` CaT
2003-08-26 16:11 ` Willy Tarreau
2003-08-26 19:32 ` Greg KH
2003-08-26 1:52 ` cryptoapi doesn't build Tom Vier
2003-08-26 10:23 ` James Morris
2003-08-27 21:49 ` Tom Vier
2003-08-27 22:03 ` Marc-Christian Petersen
2003-08-26 4:25 ` [PATCH-2.4] make log buffer length selectable Willy Tarreau
2003-08-27 20:09 ` Tom Rini
2003-08-27 20:48 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 16:25 linux-2.4.22 released Mikael Pettersson
2003-08-25 16:40 ` Marc-Christian Petersen
2003-08-25 16:53 Marcelo Tosatti
2003-08-25 17:20 Mikael Pettersson
2003-08-27 21:45 ` Marc-Christian Petersen
2003-08-26 22:25 John Bradford
2003-08-27 2:11 ` Ramón Rey Vicente
2003-08-27 6:10 John Bradford
2003-08-28 2:31 ` bill davidsen
2003-08-27 11:10 Vid Strpic
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=1061857293.15168.3.camel@debian \
--to=retes_simbad@yahoo.es \
--cc=bunk@fs.tum.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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