From: Robert Love <rml@tech9.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-ia64@linuxia64.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-pre6 drm-4.0
Date: 07 Dec 2001 18:42:10 -0500 [thread overview]
Message-ID: <1007768531.12114.2.camel@phantasy> (raw)
In-Reply-To: <4719.1007767953@ocs3.intra.ocs.com.au>
In-Reply-To: <4719.1007767953@ocs3.intra.ocs.com.au>
On Fri, 2001-12-07 at 18:32, Keith Owens wrote:
> On 07 Dec 2001 18:27:11 -0500, Robert Love <rml@tech9.net> wrote:
> >For 2.5, there probably is no intention of keeping that around. But can
> >we honestly ditch it in the middle of a stable kernel? Personally I
> >don't use it, but its not polite ...
> Linus ditched drm 4.0 months ago. It only survives in arch add on
> patches like ia64 and in -ac trees.
I know. I meant we should continue to support the drm-4.0 package.
It's the usual song ... we shouldn't change interfaces or required tools
in a stable series, and the least we can do is make 4.0 available
somehow, because someone may rely on it.
On the flip side, I don't care, and I suspect the people who actually
are using DRM are on 4.1 now. Further, if _you_ are maintaining the
cruft and it bothers _you_, then stop :)
Robert Love
next prev parent reply other threads:[~2001-12-07 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 23:20 Linux 2.4.17-pre6 drm-4.0 Keith Owens
2001-12-07 23:27 ` Robert Love
2001-12-07 23:32 ` Keith Owens
2001-12-07 23:42 ` Robert Love [this message]
2001-12-08 0:12 ` Barry K. Nathan
2001-12-08 1:03 ` Eyal Lebedinsky
2001-12-08 11:35 ` Alan Cox
2001-12-07 23:38 ` [Linux-ia64] " David Mosberger
2001-12-08 0:25 ` Keith Owens
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` [Linux-ia64] " Christoph Hellwig
2001-12-08 15:34 ` Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
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=1007768531.12114.2.camel@phantasy \
--to=rml@tech9.net \
--cc=kaos@ocs.com.au \
--cc=linux-ia64@linuxia64.org \
--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 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.