public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: neuron <neuron@hollowtube.mine.nu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r1 ready to go stable on all archs
Date: Tue, 12 Oct 2004 01:00:52 +0200	[thread overview]
Message-ID: <416B10A4.7080807@hollowtube.mine.nu> (raw)
In-Reply-To: <1097526348.30232.6.camel@helen.science.oregonstate.edu>

I and quite a lot of other people noticed a massive slowdown when 
switching to xorg, I gave up trying to track down the reason for this 
slowdown and my laptop (which was the only box on ~x86) is now testing 
ubuntu.

I noticed in the xorg thread on the message forum:

"I was having the same "really slow" loading problems experienced by 
others here using 6.8.0-r1, but that seems to be fixed with the latest 
masked release (6.8.0-r2). Now applications (X. KDE, etc) load as fast 
or faster then the 6.7.0-r2 release. I'm using the latest nvidia kernel 
release. Great job!"

So PLEASE dont mark 6.8.0-r1 stable, I had major issues with that one.

>If there's anything I absolutely need to get in before xorg-x11-6.8.0-r1
>can be marked stable on all archs, let me know within 24 hours. I plan
>to mark x86 stable Tuesday night PDT and would like other archs to
>follow shortly thereafter unless there's something I don't know about.
>And yeah, I'll file you arch maintainers a bug for it so no need to
>complain about list-only notices. =P
>
>I'd like to have a few days in stable before the snapshot for 2004.3 is
>taken.
>
>Thanks,
>Donnie
>  
>


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-10-11 23:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 20:25 [gentoo-dev] xorg-x11-6.8.0-r1 ready to go stable on all archs Donnie Berkholz
2004-10-11 21:47 ` Stuart Bouyer
2004-10-11 20:57   ` Donnie Berkholz
2004-10-11 21:54   ` Mike Frysinger
2004-10-11 22:50     ` Daniel Goller
2004-10-11 21:52       ` Donnie Berkholz
2004-10-11 22:58         ` Luke-Jr
2004-10-11 22:04           ` Donnie Berkholz
2004-10-12  3:43             ` Daniel Goller
2004-10-12  8:47               ` Mike Williams
2004-10-11 21:53 ` Lars Weiler
2004-10-11 21:10   ` Donnie Berkholz
2004-10-11 22:43     ` Lars Weiler
2004-10-12 13:43     ` Paul de Vrieze
2004-10-12 14:09   ` Lars Weiler
2004-10-11 22:21 ` Luke-Jr
2004-10-11 21:27   ` Donnie Berkholz
2004-10-11 22:39     ` Luke-Jr
2004-10-11 21:47       ` Donnie Berkholz
2004-10-12  9:01         ` Christian Parpart
2004-10-12 10:01           ` [gentoo-dev] " Sebastian Bergmann
2004-10-12 14:48             ` Donnie Berkholz
2004-10-11 23:00 ` neuron [this message]
2004-10-12 10:36 ` [gentoo-dev] " Henrik Brix Andersen
2004-10-16  4:53 ` Lance Albertson
2004-10-16  8:32   ` Stefan Schweizer
2004-10-17 11:25     ` Henrik Brix Andersen
2004-10-16 10:08   ` [gentoo-dev] " Duncan
2004-10-16 19:22 ` [gentoo-dev] " Carsten Lohrke
2004-10-17  3:25   ` Donnie Berkholz
2004-10-17 12:37     ` Carsten Lohrke

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=416B10A4.7080807@hollowtube.mine.nu \
    --to=neuron@hollowtube.mine.nu \
    --cc=gentoo-dev@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