<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.5" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Remi's Blog - Latest comments</title>
		<link>http://blogs.gentoo.org/remi?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.5"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: Xorg-server 1.7 in ~arch</title>
			<pubDate>Tue, 03 Nov 2009 21:33:14 +0000</pubDate>
			<dc:creator>Octavian [Visitor]</dc:creator>
			<guid isPermaLink="false">c23948@http://blogs.gentoo.org/</guid>
			<description>Just installed xorg 1.7.1.&lt;br /&gt;
Am I dreaming or this new xorg is much faster than the 1.6?&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;&lt;em&gt;R&amp;#233;mi: if you're using the Intel driver, there's a pretty good chance it'll be much faster. 2.9 will even be a little faster when we stabilize it :)&lt;/em&gt;&lt;/strong&gt;</description>
			<content:encoded><![CDATA[Just installed xorg 1.7.1.<br />
Am I dreaming or this new xorg is much faster than the 1.6?<br />
<br />
<strong><em>R&#233;mi: if you're using the Intel driver, there's a pretty good chance it'll be much faster. 2.9 will even be a little faster when we stabilize it :)</em></strong>]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/26/xorg-server-1-7-unmasking#c23948</link>
		</item>
				<item>
			<title>In response to: Response to a comment</title>
			<pubDate>Tue, 03 Nov 2009 00:29:17 +0000</pubDate>
			<dc:creator>dmk [Visitor]</dc:creator>
			<guid isPermaLink="false">c23933@http://blogs.gentoo.org/</guid>
			<description>not to forget, that you can't and shouldn't fix ''upstream'' in the distro. as a distro you just serve ''upstream'' as best as possible to your users. .</description>
			<content:encoded><![CDATA[not to forget, that you can't and shouldn't fix ''upstream'' in the distro. as a distro you just serve ''upstream'' as best as possible to your users. .]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/29/response-to-a-comment#c23933</link>
		</item>
				<item>
			<title>In response to: Xorg-server 1.7 in ~arch</title>
			<pubDate>Mon, 02 Nov 2009 02:50:27 +0000</pubDate>
			<dc:creator>Jake [Visitor]</dc:creator>
			<guid isPermaLink="false">c23864@http://blogs.gentoo.org/</guid>
			<description>Um.. wow, scratch that last stupid comment I made.  Everyone makes typos right?  &lt;br /&gt;
The newest x11 drivers DO work...</description>
			<content:encoded><![CDATA[Um.. wow, scratch that last stupid comment I made.  Everyone makes typos right?  <br />
The newest x11 drivers DO work...]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/26/xorg-server-1-7-unmasking#c23864</link>
		</item>
				<item>
			<title>In response to: Xorg-server 1.7 in ~arch</title>
			<pubDate>Mon, 02 Nov 2009 02:05:09 +0000</pubDate>
			<dc:creator>Jake [Visitor]</dc:creator>
			<guid isPermaLink="false">c23861@http://blogs.gentoo.org/</guid>
			<description>So... anyone care to shed a light on why none of the x11 drivers work with the new xorg-server?  Seems that the dependencies haven't caught up with the newest xorg...</description>
			<content:encoded><![CDATA[So... anyone care to shed a light on why none of the x11 drivers work with the new xorg-server?  Seems that the dependencies haven't caught up with the newest xorg...]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/26/xorg-server-1-7-unmasking#c23861</link>
		</item>
				<item>
			<title>In response to: Response to a comment</title>
			<pubDate>Sat, 31 Oct 2009 03:05:47 +0000</pubDate>
			<dc:creator>Ra [Visitor]</dc:creator>
			<guid isPermaLink="false">c23792@http://blogs.gentoo.org/</guid>
			<description>This is how ~arch has to be. The not infrequently demanded &quot;stability&quot; and problem-free operation of ~arch is ridiculous. &lt;br /&gt;
&lt;br /&gt;
What should be expected is one-two different compiles and possibly running through an automated test suite, not developers wasting his precious time trying to get things polished even BEFORE it hits real installations.&lt;br /&gt;
That duty must be moved to the larger amount of installations and the overall massively larger time budget of ~arch users. This is the only efficient way to  produce a stable branch, after all...</description>
			<content:encoded><![CDATA[This is how ~arch has to be. The not infrequently demanded "stability" and problem-free operation of ~arch is ridiculous. <br />
<br />
What should be expected is one-two different compiles and possibly running through an automated test suite, not developers wasting his precious time trying to get things polished even BEFORE it hits real installations.<br />
That duty must be moved to the larger amount of installations and the overall massively larger time budget of ~arch users. This is the only efficient way to  produce a stable branch, after all...]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/29/response-to-a-comment#c23792</link>
		</item>
				<item>
			<title>In response to: Response to a comment</title>
			<pubDate>Thu, 29 Oct 2009 15:26:33 +0000</pubDate>
			<dc:creator>Nirbheek Chauhan [Visitor]</dc:creator>
			<guid isPermaLink="false">c23765@http://blogs.gentoo.org/</guid>
			<description>@Jeremy: I think it varies from arch-to-arch. However, x86 &amp;amp; amd64 are arches that should be easy to find ATs for.</description>
			<content:encoded><![CDATA[@Jeremy: I think it varies from arch-to-arch. However, x86 &amp; amd64 are arches that should be easy to find ATs for.]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/29/response-to-a-comment#c23765</link>
		</item>
				<item>
			<title>In response to: Response to a comment</title>
			<pubDate>Thu, 29 Oct 2009 14:12:24 +0000</pubDate>
			<dc:creator>Jeremy Olexa [Visitor]</dc:creator>
			<guid isPermaLink="false">c23762@http://blogs.gentoo.org/</guid>
			<description>Nice post. Yes, we shouldn't break the ~arch tree on purpose..But it seems like people just want a second stable tree which doesn't help us with much. But it does point out that the arch teams are overworked because they can't keep up (or we are not filing stablereqs in a timely manor, etc)</description>
			<content:encoded><![CDATA[Nice post. Yes, we shouldn't break the ~arch tree on purpose..But it seems like people just want a second stable tree which doesn't help us with much. But it does point out that the arch teams are overworked because they can't keep up (or we are not filing stablereqs in a timely manor, etc)]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/29/response-to-a-comment#c23762</link>
		</item>
				<item>
			<title>In response to: Response to a comment</title>
			<pubDate>Thu, 29 Oct 2009 12:44:27 +0000</pubDate>
			<dc:creator>Gokdeniz Karadag [Visitor]</dc:creator>
			<guid isPermaLink="false">c23759@http://blogs.gentoo.org/</guid>
			<description>Hi,&lt;br /&gt;
&lt;br /&gt;
Thanks for the effort on keeping up with X.&lt;br /&gt;
&lt;br /&gt;
Also, keeping it cool and civil is a great way to respond to -positive and negative- criticism. After all, people criticise because they give importance and want things to be better.</description>
			<content:encoded><![CDATA[Hi,<br />
<br />
Thanks for the effort on keeping up with X.<br />
<br />
Also, keeping it cool and civil is a great way to respond to -positive and negative- criticism. After all, people criticise because they give importance and want things to be better.]]></content:encoded>
			<link>http://blogs.gentoo.org/remi/2009/10/29/response-to-a-comment#c23759</link>
		</item>
			</channel>
</rss>
