mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-pre6 drm-4.0
Date: Sat, 08 Dec 2001 12:03:58 +1100	[thread overview]
Message-ID: <3C1166FE.C03F0597@eyal.emu.id.au> (raw)
In-Reply-To: <4719.1007767953@ocs3.intra.ocs.com.au>

Keith Owens wrote:
> 
> On 07 Dec 2001 18:27:11 -0500,
> Robert Love <rml@tech9.net> wrote:
> >On Fri, 2001-12-07 at 18:20, Keith Owens wrote:
> >
> >> How long do people plan to keep drm 4.0 code in their versions of the
> >> kernel?
> >
> >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.

Well, I am on Debian stable, and the only Xfree4 contributed packages
are for 4.0.

I will move on to 4.1 when Debian moves on, but as you know they are
slower than a tired snail when it comes to new releases.

I wonder how many other people use these 4.0 packages off:

deb ftp://debian.cri74.org/debian-cri potato/contrib_luis_sismeiro main
non-free

--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.anu.edu.au/eyal/>

  parent reply	other threads:[~2001-12-08  1:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 23:20 Keith Owens
2001-12-07 23:27 ` Robert Love
2001-12-07 23:32   ` Keith Owens
2001-12-07 23:42     ` Robert Love
2001-12-08  0:12     ` Barry K. Nathan
2001-12-08  1:03     ` Eyal Lebedinsky [this message]
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=3C1166FE.C03F0597@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --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

all inboxes | Powered by JetHome®