From: Dave Jones <davej@redhat.com>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Keith Whitwell <keith@tungstengraphics.com>,
Ian Romanick <idr@us.ibm.com>, Dave Airlie <airlied@linux.ie>,
"DRI developer's list" <dri-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: DRM function pointer work..
Date: Sat, 7 Aug 2004 23:42:34 +0100 [thread overview]
Message-ID: <20040807224234.GD26791@redhat.com> (raw)
In-Reply-To: <20040806174645.77462.qmail@web14924.mail.yahoo.com>
On Fri, Aug 06, 2004 at 10:46:45AM -0700, Jon Smirl wrote:
> There are three main ways to get a driver:
> 1) vendor release - most stable, I get one every two weeks
> 2) Linus bk - very up to date, not as well tested, once a day
> 3) copy DRM CVS into Linus bk - bleeding edge, hope you know what you
> are doing.
In the case of bleeding edge Fedora, (Ie FC3 t1 right now), 1 and 2 are
the same. Ie, we rebase to the upstream -bk release almost daily.
(The only time we don't is when both myself and Arjan are otherwise
occupied, like recently at OLS etc, but it's rare that both of us
are too busy to do a rebase).
The current release version of Fedora (Ie, FC2 right now) has a slightly
less aggressive update cycle, typically only when either a) the upstream
kernel has fixed a lot of bugs that have been biting users, or b) there's
a security problem to justify another update.
Dave
next prev parent reply other threads:[~2004-08-07 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040806024907.13024.qmail@web14923.mail.yahoo.com>
2004-08-06 16:32 ` DRM function pointer work Ian Romanick
2004-08-06 16:54 ` Keith Whitwell
2004-08-06 17:16 ` Jon Smirl
2004-08-06 17:20 ` Keith Whitwell
2004-08-06 17:46 ` Jon Smirl
2004-08-07 22:42 ` Dave Jones [this message]
2004-08-06 17:24 ` Keith Whitwell
2004-08-06 17:48 ` Jon Smirl
2004-08-07 0:11 ` Dave Airlie
2004-08-07 14:47 ` Christoph Hellwig
2004-08-07 13:31 ` Alan Cox
2004-08-07 14:48 ` Christoph Hellwig
2004-08-07 14:46 ` Christoph Hellwig
[not found] <Pine.LNX.4.58.0408031427540.31513@skynet>
[not found] ` <Pine.LNX.4.58.0408041201490.30393@skynet>
[not found] ` <41128B90.5070702@us.ibm.com>
[not found] ` <Pine.LNX.4.58.0408052338010.9947@skynet>
[not found] ` <4112C09B.1070603@us.ibm.com>
2004-08-05 23:54 ` Dave Airlie
2004-08-07 14:43 ` 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=20040807224234.GD26791@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.com \
--cc=jonsmirl@yahoo.com \
--cc=keith@tungstengraphics.com \
--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.