LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Roman Zippel <zippel@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
Date: Tue, 20 Feb 2007 18:23:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702201820400.11849@localhost.localdomain> (raw)
In-Reply-To: <45DB805C.5010808@imap.cc>
On Wed, 21 Feb 2007, Tilman Schmidt wrote:
> Am 20.02.2007 23:52 schrieb Robert P. J. Day:
> > "deprecated" means that there *is* a complete replacement available
> > *right now* and you should consider switching to it.
> >
> > if you can't offer someone a completely functional, better alternative
> > to what they're using now, then you can't say that what they're using
> > now is deprecated.
>
> So, to take a specific example (incidentally the one I am
> personally interested in):
>
> isdn4linux (CONFIG_ISDN_I4L), currently marked as "obsolete"
> (which is undoubtedly incorrect), would not even qualify as
> "deprecated" as long as its successor, the CAPI 2.0 subsystem
> (CONFIG_ISDN_CAPI) doesn't support all the hardware currently
> supported by old i4l.
>
> Or did I misunderstand something there?
IMHO, unless you have a fully-functional replacement ready to go, you
can't call something "deprecated" much less "obsolete". so, yes,
calling isdn4linux "obsolete" is hideously premature.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-02-20 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 17:06 Robert P. J. Day
2007-02-18 18:35 ` Bartlomiej Zolnierkiewicz
2007-02-18 18:53 ` Robert P. J. Day
2007-02-20 16:27 ` Tilman Schmidt
2007-02-20 18:42 ` Bartlomiej Zolnierkiewicz
2007-02-20 22:52 ` Robert P. J. Day
2007-02-20 23:12 ` Tilman Schmidt
2007-02-20 23:23 ` Robert P. J. Day [this message]
2007-02-25 10:42 ` Pavel Machek
2007-02-25 22:59 ` Tilman Schmidt
2007-02-20 22:47 ` Robert P. J. Day
2007-02-20 22:56 ` Sam Ravnborg
2007-02-20 23:01 ` Robert P. J. Day
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=Pine.LNX.4.64.0702201820400.11849@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
--cc=zippel@linux-m68k.org \
--subject='Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).