From: Tilman Schmidt <tilman@imap.cc>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
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: Sun, 25 Feb 2007 23:59:21 +0100 [thread overview]
Message-ID: <45E214C9.5050709@imap.cc> (raw)
In-Reply-To: <20070225104255.GD2045@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Am 25.02.2007 11:42 schrieb Pavel Machek:
> On Wed 2007-02-21 00:12:28, 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.
>
> It probably never will. Some hardware is so obsolete that noone will
> care :-).
s/supported by/in active use with/
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-02-25 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 17:06 [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE 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
2007-02-25 10:42 ` Pavel Machek
2007-02-25 22:59 ` Tilman Schmidt [this message]
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=45E214C9.5050709@imap.cc \
--to=tilman@imap.cc \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpjday@mindspring.com \
--cc=zippel@linux-m68k.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 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.