From: "Ramón Rey Vicente" <retes_simbad@yahoo.es>
To: John Bradford <john@grabjohn.com>
Cc: aradorlinux@yahoo.es, bunk@fs.tum.de, jamagallon@able.es,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.22 released
Date: Wed, 27 Aug 2003 04:11:47 +0200 [thread overview]
Message-ID: <1061950306.1161.37.camel@debian> (raw)
In-Reply-To: <200308262225.h7QMPe0J000367@81-2-122-30.bradfords.org.uk>
El mié, 27-08-2003 a las 00:25, John Bradford escribió:
> I think the 'more urgent things to be fixed' point is important.
Well, Linux is used in many circunstances, for desktop, for
workstations, for servers, every user have a specific "urgent thing"
> Only a certain amount of patches can go in to 2.4.23 if we want to
> keep this a short development cycle, and efforts to stabilise 2.4 so
> that embedded users who are still using 2.2 have something to migrate
> to are important.
why shorts development cycles? Stable development cycles must be long
cycles for test every change... If embedded users are still using 2.2,
stabilising 2.4 is important as much as keeping up to date the drivers
for desktop users and support new hardware I think...
--
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-27 2:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 22:25 linux-2.4.22 released John Bradford
2003-08-27 2:11 ` Ramón Rey Vicente [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 11:10 Vid Strpic
2003-08-27 6:10 John Bradford
2003-08-28 2:31 ` bill davidsen
2003-08-25 17:20 Mikael Pettersson
2003-08-27 21:45 ` Marc-Christian Petersen
2003-08-25 16:53 Marcelo Tosatti
2003-08-25 16:25 Mikael Pettersson
2003-08-25 16:40 ` Marc-Christian Petersen
2003-08-25 11:48 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
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
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=1061950306.1161.37.camel@debian \
--to=retes_simbad@yahoo.es \
--cc=aradorlinux@yahoo.es \
--cc=bunk@fs.tum.de \
--cc=jamagallon@able.es \
--cc=john@grabjohn.com \
--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