From: "Ramón Rey Vicente" <retes_simbad@yahoo.es>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.21 released
Date: 14 Jun 2003 23:58:58 +0200 [thread overview]
Message-ID: <1055627935.4965.6.camel@debian> (raw)
In-Reply-To: <20030614233527.08831e2a.diegocg@teleline.es>
El s?, 14-06-2003 a las 23:35, Diego Calleja García escribió:
> On Fri, 13 Jun 2003 18:29:24 +0100
> Christoph Hellwig <hch@infradead.org> wrote:
>
> > On Fri, Jun 13, 2003 at 07:22:26PM +0200, Matthias Andree wrote:
> > > I'd add "XFS merge" to the list:
> >
> > I'll start feeding the few remaining core changes to Marcelo now,
> > the actual filesystem then is just yet another driver that could
> > be merged any time :)
>
> Just a small suggestion: Why not ALSA?
> I mean, 2.5 is there for new things, indeed. But alsa are drivers (ie: it
> shouldnt affect core code and you haven't to use them if you don't want) ,
> and after all it's one of those things that lots of people have to add (a
> lot of times manually and lots of people doesn't want to know how to patch
> a kernel; although all distros ship it).
I think 2.4.x series are stable versions, but on the past we saw how new
code was added to the linux stable tree if that code wasn't invasive.
ALSA have many advantages and improved coded compared with OSS, and
could add support for a few new devices. I think ALSA is an interesting
thing now, when ALSA seems very stable.
--
/================================================\
| Ramón Rey Vicente <ramon.rey at hispalinux.es> |
| |
| Jabber ID <rreylinux at jabber.org> |
| |
| Public GPG Key http://pgp.escomposlinux.org |
| |
| GLiSa http://glisa.hispalinux.es |
\================================================/
next prev parent reply other threads:[~2003-06-14 21:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 14:53 linux-2.4.21 released Marcelo Tosatti
2003-06-13 16:56 ` Stefan Foerster
2003-06-13 16:56 ` Damian Kolkowski
2003-06-13 17:37 ` Stephan von Krawczynski
2003-06-13 17:19 ` Damian Kołkowski
2003-06-13 17:49 ` Alan Cox
2003-06-13 17:45 ` Damian Kolkowski
2003-06-13 18:36 ` Damian Kołkowski
2003-06-13 21:04 ` Daniel Egger
2003-06-13 21:31 ` Damian Kołkowski
2003-06-15 14:29 ` Daniel Egger
2003-06-14 15:59 ` Krzysiek Taraszka
2003-06-14 16:16 ` Damian Kołkowski
2003-06-13 18:10 ` Serguei Miridonov
2003-06-13 17:22 ` Matthias Andree
2003-06-13 17:29 ` Christoph Hellwig
2003-06-14 21:35 ` Diego Calleja García
2003-06-14 21:58 ` Ramón Rey Vicente [this message]
2003-06-15 12:02 ` Matthias Andree
2003-06-13 18:56 ` Ramón Rey Vicenteey Vicente
2003-06-13 20:03 ` Robert Love
2003-06-13 20:27 ` Ramón Rey Vicente
2003-06-13 21:50 ` J.A. Magallon
2003-06-14 7:31 ` Wiktor Wodecki
2003-06-13 19:14 ` Udo A. Steinberg
2003-06-13 19:24 ` Ross Biro
2003-06-14 2:02 ` Andrea Arcangeli
2003-06-14 4:28 ` Ben Collins
2003-06-14 15:36 ` CJ
2003-06-14 15:54 ` Jörn Engel
2003-06-14 16:29 ` CJ
2003-06-15 19:06 ` Jörn Engel
2003-06-15 19:49 ` linux-2.4.21 released , No changelog for sym53c8xx_2 mods ? Mr. James W. Laferriere
2003-06-16 22:22 ` linux-2.4.21 released Lukasz Trabinski
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 16:40 Go Marcelo
2003-06-16 0:34 Fr�d�ric L. W. Meunier
2003-06-22 18:51 Fr�d�ric L. W. Meunier
2003-06-22 19:46 Nicolas Mailhot
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=1055627935.4965.6.camel@debian \
--to=retes_simbad@yahoo.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