public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: xorg-x11-6.8.0-r4 needs testers
Date: Wed, 24 Nov 2004 04:41:22 -0700	[thread overview]
Message-ID: <pan.2004.11.24.11.41.22.12494@cox.net> (raw)
In-Reply-To: pan.2004.11.24.06.01.03.866847@cox.net

Duncan posted <pan.2004.11.24.06.01.03.866847@cox.net>, excerpted below, 
on Tue, 23 Nov 2004 23:01:04 -0700:

> Donnie Berkholz posted as excerpted:
> 
>> 67845: Fix dual-monitor Radeon setups
> 
> s/84/48/ .  The bug is 67485, not 67845.  (I'm running dual monitor Radeon
> 9200SE w/ the xorg free drivers here so was interested in this one.  I had
> to search...)
> 
> I haven't had this issue, but I've had MonitorLayout all along.
> 
> I think I'll be merging this -r4 over Thanksgiving if not 2nite

Posting on -r4 now, on amd64.  Seems to work fine, including the dual
monitors on Radeon (atho as above I have MonitorLayout as I always have).
Note that I modify the ebuild, turning off compilation of a lot of the
stuff I don't need, however (and even more now with -r4), and commenting
out the strip-flags call, so I wasn't testing a regular merge.

That said, the general ebuild including the moved stuff seems to work fine
on amd64.

I assume you know it can't find some of the sources, the koi8 font for
USE=nls and the extra sources for USE=doc, right?  I remember having to
kill those lines to digest r1 as well, so the problem has been around for
awhile.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-11-24 11:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 23:01 [gentoo-dev] xorg-x11-6.8.0-r4 needs testers Donnie Berkholz
2004-11-18  0:14 ` Ciaran McCreesh
2004-11-21 14:41   ` Ned Ludd
2004-11-18 14:10 ` Chris Gianelloni
2004-11-18 15:39   ` Ciaran McCreesh
2004-11-18 16:21     ` Chris Gianelloni
2004-11-18 17:01       ` Ciaran McCreesh
2004-11-18 19:34         ` Chris Gianelloni
2004-11-18 17:08   ` Donnie Berkholz
2004-11-18 17:13     ` Donnie Berkholz
2004-11-18 20:57       ` Ferris McCormick
2004-11-18 18:50     ` Donnie Berkholz
2004-11-18 20:31       ` Chris Gianelloni
2004-11-18 19:58         ` Donnie Berkholz
2004-11-18 21:08           ` Chris Gianelloni
2004-11-18 21:18           ` Chris Gianelloni
2004-11-18 20:26             ` Donnie Berkholz
2004-11-18 21:32               ` Chris Gianelloni
2004-11-18 20:31     ` Joseph Booker
2004-11-18 20:28       ` Donnie Berkholz
2004-11-24 21:45       ` Henrik Brix Andersen
2004-11-19 10:02     ` Paul de Vrieze
2004-11-19 16:44       ` Donnie Berkholz
2004-11-21 23:31     ` Donnie Berkholz
2004-11-18 17:45 ` Michiel de Bruijne
2004-11-18 17:47   ` Donnie Berkholz
2004-11-18 17:58     ` Michiel de Bruijne
2004-11-18 17:58       ` Donnie Berkholz
2004-11-18 18:26         ` Marcus D. Hanwell
2004-11-19 23:13         ` Michiel de Bruijne
2004-11-23  6:50 ` Gábor Farkas
2004-11-23 12:19   ` Jason Stubbs
2004-11-24  6:01 ` [gentoo-dev] " Duncan
2004-11-24 11:41   ` Duncan [this message]
2004-11-24 17:00     ` Donnie Berkholz
2004-11-24 12:33 ` [gentoo-dev] " Aaron Walker

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=pan.2004.11.24.11.41.22.12494@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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