public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] update OBSOLETE_OSS_DRIVER schedule and dependencies
Date: Sun, 12 Feb 2006 18:20:24 +0100	[thread overview]
Message-ID: <20060212172024.GI30922@stusta.de> (raw)
In-Reply-To: <1139709891.23823.4.camel@localhost.localdomain>

On Sun, Feb 12, 2006 at 02:04:50AM +0000, Alan Cox wrote:
> On Sad, 2006-02-11 at 15:50 +0100, Adrian Bunk wrote:
> > This patch updates the schedule for the removal of drivers depending on 
> > OBSOLETE_OSS_DRIVER as follows:
> > - adjust OBSOLETE_OSS_DRIVER dependencie
> > - from the release of 2.6.16 till the release of 2.6.17:
> >   approx. two months for users to report problems with the ALSA
> >   drivers for the same hardware
> 
> Why are you obsessed with doing everything on what are (to end users)
> stupidly short time scales. It doesn't matter if OSS takes another year
> to finally go away so stop setting silly deadlines.

In my experience, scheduling things for removal at a far away date has 
nearly no effect - people still don't start complaining until it's being 
made clear that the code will really be removed, and that it will be 
removed soon.

It wouldn't be the first time that after a longer deprecation periodthe 
first person is complaining not before I'm sending the patch to remove 
the deprecated code.

In this case, we are talking about the OSS drivers with ALSA drivers for 
the same hardware. And a driver will not be removed if one person 
notifies me about one regression in the ALSA driver compared to the OSS 
driver.

And the positive effect of forcing people to report the regressions in 
ALSA drivers is already visible as improvements in the ALSA drivers.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-02-12 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 14:50 [2.6 patch] update OBSOLETE_OSS_DRIVER schedule and dependencies Adrian Bunk
2006-02-12  2:04 ` Alan Cox
2006-02-12 17:20   ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-14 23:28 Adrian Bunk

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=20060212172024.GI30922@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox