LKML Archive on
help / color / mirror / Atom feed
From: Tilman Schmidt <>
To: Alan Cox <>
Cc: David Miller <>,,,,
Subject: Re: [PATCH] Remove "obsolete" label from ISDN4Linux (v3)
Date: Sun, 22 Apr 2007 16:29:01 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2595 bytes --]

Am 22.04.2007 14:58 schrieb Alan Cox:
>>>> If it isn't obsolete then fix the code to use the newer APIs
>> Why should that be a precondition for removing the incorrect
>> "obsolete" label?
> Because if we remove the obsolete label the users are going to be
> suprised when it goes away entirely with && BROKEN or && !HOTPLUG or
> similar.

I trust that && BROKEN won't happen before it will actually *be*
obsolete and correctly re-labelled as such. As for the && !HOTPLUG
menace you keep touting, that might perhaps be applied to some of
the individual hardware device drivers but certainly not to the
I4L core itself. What you mean by "or similar" I cannot guess.
AFAIK we don't have an && EYESORE option yet. :-)

>> Any change that breaks isdn4linux before its
>> replacement is ready would constitute a regression.
>> We've been there once, remember?
> Want to be on that. There is nobody maintaining it. That isn't a
> sustainable situation so it will break.

Not sure I'm following you. There is an official maintainer, and
although he's currently rather silent on this topic, there's no
reason to believe he won't step up if there's actually some urgent
maintaining to be done.

>> [L]ack of a working replacement *is* an
>> argument for concluding that something is not obsolete.
> Ok then it should be marked "BROKEN" instead.

Is that a serious suggestion? Replace one wrong label with another,
even wronger one? I don't see how that might help.

>> - These are two independent problems. Blocking the correction of
>>   one of them because the other one still exists doesn't help,
>>   but only risks deadlock.
> No risk of deadlock. It'll progress to && BROKEN which will either cause
> sufficient pain for someone to get off their arse and fix it, for enough
> of a vendors users to get the vendor to do the work or for someone who
> cares to pay a third party to do the work.

Do I sense some hidden agenda there?

The isdn4linux subsystem will not "progress" to BROKEN unless
somebody pushes it there. It is currently working sufficiently
well for its users to fill the gap until its successor CAPI is
ready. Once that happens, it can be obsoleted, but not before.
I know people are less than happy this hasn't happened yet, but
the way to promote the move to CAPI is not to kill off I4L before
the time and leave users standing in the rain.


Tilman Schmidt                          E-Mail:
Bonn, Germany
- Undetected errors are handled as if no error occurred. (IBM) -

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  reply	other threads:[~2007-04-22 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 11:43 any value to fixing apparent bugs in old ISDN4Linux? Robert P. J. Day
2007-01-15 13:57 ` Karsten Keil
2007-01-15 17:09 ` Tilman Schmidt
2007-01-15 17:17   ` Robert P. J. Day
2007-01-15 17:29     ` Karsten Keil
2007-02-21  0:29       ` [PATCH] Remove "obsolete" label from ISDN4Linux (was: any value to fixing apparent bugs in old ISDN4Linux?) Tilman Schmidt
2007-03-28 22:18       ` [Repost][PATCH] Remove "obsolete" label from ISDN4Linux Tilman Schmidt
2007-04-21 13:07       ` [PATCH] Remove "obsolete" label from ISDN4Linux (v3) Tilman Schmidt
2007-04-21 20:58         ` Alan Cox
2007-04-21 22:10           ` David Miller
2007-04-22 12:27             ` Tilman Schmidt
2007-04-22 12:58               ` Alan Cox
2007-04-22 14:29                 ` Tilman Schmidt [this message]
2007-04-22 15:17                   ` Alan Cox
2007-04-22 15:48                     ` Satyam Sharma
2007-04-22 16:20                       ` Alan Cox
2007-04-23 23:58                         ` Tilman Schmidt
2007-05-28 16:32       ` [PATCH] ISDN4Linux: fix maturity label (v4) Tilman Schmidt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] Remove "obsolete" label from ISDN4Linux (v3)' \

* 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).