From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
"'Andrew Morton'" <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Badari Pulavarty <pbadari@us.ibm.com>
Subject: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
Date: Sat, 21 Jan 2006 01:49:17 +0000 [thread overview]
Message-ID: <1137808158.24161.64.camel@localhost.localdomain> (raw)
In-Reply-To: <20060121010229.GP31803@stusta.de>
On Sad, 2006-01-21 at 02:02 +0100, Adrian Bunk wrote:
> Why did noone tell me anythong about such issues although I'm the one
> listed as having this driver deprecated?
Because they don't spend their lives tracking the base kernel, they
expect sanity to prevail and their idea of an obsolescence cycle is
about five years.
ISV = "Independant software vendor"
Obsoleting stuff which is distribution internal configuration type stuff
(eg devfs->udev) is one thing but core syscall related stuff has to
undergo a much much longer cycle, or in many cases you just have to look
at it and treat it as a lesson for the future and a thing to tackle in
whatever OS obsoletes Linux.
Thats why 0.98.5 libc 2.2 and rogue still work on 2.6.
Alan
next prev parent reply other threads:[~2006-01-21 1:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 3:02 [2.6 patch] the scheduled removal of the obsolete raw driver Adrian Bunk
2006-01-19 3:41 ` Andrew Morton
2006-01-19 5:43 ` Chen, Kenneth W
2006-01-21 1:02 ` Adrian Bunk
2006-01-21 1:08 ` Chen, Kenneth W
2006-01-21 1:49 ` Alan Cox [this message]
2006-01-19 16:10 ` Adrian Bunk
2006-01-19 16:44 ` Badari Pulavarty
2006-01-19 16:52 ` Mark Lord
2006-01-19 16:58 ` Adrian Bunk
2006-01-19 18:14 ` Badari Pulavarty
2006-01-20 8:24 ` [SARCASM] " Ingo Oeser
2006-01-20 14:02 ` Jan Engelhardt
2006-01-22 12:51 ` [OT] " Alexander E. Patrakov
2006-01-21 8:52 ` Arjan van de Ven
2006-01-21 19:41 ` Dave Jones
2006-01-21 21:17 ` Andrew Morton
2006-01-21 21:25 ` Arjan van de Ven
2006-01-21 21:35 ` Andrew Morton
2006-01-21 21:50 ` Arjan van de Ven
2006-01-22 17:50 ` Jesper Juhl
2006-01-21 23:26 ` Gene Heskett
2006-01-21 23:30 ` Lee Revell
2006-01-21 23:53 ` Gene Heskett
2006-01-21 23:59 ` Doug McNaught
2006-01-22 0:09 ` Gene Heskett
2006-01-22 0:15 ` Lee Revell
2006-01-22 1:30 ` Doug McNaught
2006-01-22 8:14 ` Arjan van de Ven
2006-01-22 20:33 ` Alan Cox
2006-01-22 21:53 ` Jan Engelhardt
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=1137808158.24161.64.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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.