From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Big thanks to spyderous
Date: Thu, 06 Jul 2006 10:44:44 -0700 [thread overview]
Message-ID: <1152207884.26453.9.camel@neuromancer.home.net> (raw)
In-Reply-To: <44ACCFC1.4080604@gentoo.org>
On Thu, 2006-07-06 at 01:54 -0700, Donnie Berkholz wrote:
> Ow Mun Heng wrote:
> > I'm still stucked on Xorg-6.8 and not intending to upgrade anytime soon
> > unless there is a lot of good things to expect out of it.
> > Right now, as long as there's no exploit/bug for xorg-6.8, I'll keep it
> > that way.
>
> Yep, that's your prerogative. But the next exploit may not get updated
> in 6.x.
Don't get me wrong, it's not that I don't want to upgrade, I just don't
have a test box and I just don't want to go through some "hell" to get
my laptop to work for work. :-)
> There are plenty of improvements to expect, but you'd need to
> read the ChangeLogs for details.
Which changelogs? Xorgs or the one in portage?
I can't seem to find the changelogs for xorg 7.0 in www.x.org.
> Addition of the new acceleration
> architecture (exa), accelerated indirect GLX, and many fixes to drivers
> are just a few.
I see, you mean xorg's changelogs.
I just looked at the modular x upgrade howto and the wiki, seems pretty
decent.
But the Block List and the # of packages is just huge :-)
What are the caveats during the upgrade?
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-07-06 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 16:51 [gentoo-user] Big thanks to spyderous Richard Fish
2006-07-05 17:33 ` fire-eyes
2006-07-05 20:45 ` John J. Foster
2006-07-06 4:19 ` Donnie Berkholz
2006-07-06 8:35 ` Ow Mun Heng
2006-07-06 8:54 ` Donnie Berkholz
2006-07-06 17:44 ` Ow Mun Heng [this message]
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=1152207884.26453.9.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--cc=gentoo-user@lists.gentoo.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