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

> >> 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

> >> to end up && BROKEN let alone Obsolete.
> That can't happen. 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.

> I beg to differ. Existence of a working replacement is exactly
> the criterion we arrived at when discussing the meaning of the
> term "obsolete". So lack of a working replacement *is* an
> argument for concluding that something is not obsolete.

Ok then it should be marked "BROKEN" instead.

> - The authors of certain in-kernel API changes seem to have
>   neglected the isdn4linux subsystem in their work.

For simile changes they have kept it going (eg the tty changes), but the
code is too big and too messy for that to happen for all things. Thus
it will eventually break

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


  reply	other threads:[~2007-04-22 12:55 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 [this message]
2007-04-22 14:29                 ` Tilman Schmidt
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).