From: Daniel Goller <morfic@gentoo.org>
To: Donnie Berkholz <spyderous@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r1 ready to go stable on all archs
Date: Mon, 11 Oct 2004 22:43:46 -0500 [thread overview]
Message-ID: <416B52F2.8000702@gentoo.org> (raw)
In-Reply-To: <1097532277.30232.49.camel@helen.science.oregonstate.edu>
the block would help them see that they cant use 3.x.y unless it is
given a all clear by xorg and ati-drivers teams
ie, dont waste people trying one with the other until it works, those
who can try will anyway and those not capable to step out side the box
will appreciate not fighting xorg 6.8.0-r1 until working ati-drivers
exist, like luke-jr said, dont block a certain version or range, block
it altogether
Donnie Berkholz wrote:
>On Mon, 2004-10-11 at 15:58, Luke-Jr wrote:
>
>
>>On Monday 11 October 2004 9:52 pm, Donnie Berkholz wrote:
>>
>>
>>>On Mon, 2004-10-11 at 15:50, Daniel Goller wrote:
>>>
>>>
>>>>Guess it is simpler to block on ati-drivers till ati-drivers are fixed.
>>>>But to push 6.8.0-r1 out for anyone to upgrade knowing it will cause
>>>>chaos doesn't seem wise.
>>>>
>>>>
>>>How exactly would you like me to do this? I can't block below a specific
>>>version, because I don't know whether the next one released will work. I
>>>can't block all versions, because then they'll never be able to install
>>>one that does work.
>>>
>>>
>>Any reason you can't block all versions and have the ati-drivers people modify
>>the block to include a specific version once one works?
>>
>>
>
>Think: Will that help people who have already emerged an ebuild that
>blocks all versions? I'd need a revision bump to change it, which is a
>complete waste.
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-12 3:39 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 [this message]
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 ` [gentoo-dev] " neuron
2004-10-12 10:36 ` 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=416B52F2.8000702@gentoo.org \
--to=morfic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=spyderous@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