public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0
Date: Fri, 07 Dec 2001 23:42:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805657@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805654@msgid-missing>

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



  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:27 [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0 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 11:35 ` Alan Cox
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` Christoph Hellwig
2001-12-08 15:34 ` Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
2001-12-14 19:13 ` David Mosberger
2001-12-15 10:19 ` Christoph Hellwig
2001-12-17 16:14 ` Marcelo Tosatti
2001-12-17 22:46 ` Juan Quintela

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=marc-linux-ia64-105590698805657@msgid-missing \
    --to=rml@tech9.net \
    --cc=linux-ia64@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