<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Labix Blog</title>
	<atom:link href="http://blog.labix.org/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.labix.org</link>
	<description>by Gustavo Niemeyer</description>
	<lastBuildDate>Mon, 16 Jan 2012 12:12:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Bazaar, the git way by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119067</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Mon, 16 Jan 2012 12:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119067</guid>
		<description>Jelmer, it sounds like a good idea indeed. Will put that in the next release.</description>
		<content:encoded><![CDATA[<p>Jelmer, it sounds like a good idea indeed. Will put that in the next release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Jelmer Vernooij</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119065</link>
		<dc:creator>Jelmer Vernooij</dc:creator>
		<pubDate>Mon, 16 Jan 2012 12:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119065</guid>
		<description>Argh, race condition. I didn&#039;t see your reply until I posted mine.

It would be nice if cobzr could back off if .bzr/branches existed, so that it will seamlessly work with the new colocated branch support if that has been enabled on a bzr control directory.</description>
		<content:encoded><![CDATA[<p>Argh, race condition. I didn&#8217;t see your reply until I posted mine.</p>
<p>It would be nice if cobzr could back off if .bzr/branches existed, so that it will seamlessly work with the new colocated branch support if that has been enabled on a bzr control directory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119064</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Mon, 16 Jan 2012 11:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119064</guid>
		<description>Jelmer, I hope it&#039;s clear that I&#039;m looking forward to that! :-)

Regarding the use of .bzr/branches, I explicitly avoided it because I noticed you were using it for the upcoming 2.5 functionality. .bzr/cobzr felt like it wouldn&#039;t cause trouble to anyone.</description>
		<content:encoded><![CDATA[<p>Jelmer, I hope it&#8217;s clear that I&#8217;m looking forward to that! <img src='http://blog.labix.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Regarding the use of .bzr/branches, I explicitly avoided it because I noticed you were using it for the upcoming 2.5 functionality. .bzr/cobzr felt like it wouldn&#8217;t cause trouble to anyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Jelmer Vernooij</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119063</link>
		<dc:creator>Jelmer Vernooij</dc:creator>
		<pubDate>Mon, 16 Jan 2012 11:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119063</guid>
		<description>Oh, and of course it integrates with the &quot;normal&quot; commands rather than adding a new set. That&#039;s pretty neat.

We&#039;ll make sure to obsolete it before long though, by finishing the colocated branch support in core. ;-)</description>
		<content:encoded><![CDATA[<p>Oh, and of course it integrates with the &#8220;normal&#8221; commands rather than adding a new set. That&#8217;s pretty neat.</p>
<p>We&#8217;ll make sure to obsolete it before long though, by finishing the colocated branch support in core. <img src='http://blog.labix.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119062</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Mon, 16 Jan 2012 11:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119062</guid>
		<description>Sorry, I forgot to mention it here, but the page does mention it at the top:

&lt;blockquote&gt;
There&#039;s also a plugin (link) available offering similar functionality. cobzr differs from the plugin by using a command set similar to git and by hiding away the visible difference between a branch with co-location and one without. Commands always work, and the tree is adapted to co-location the first time multiple branches are requested, so usage is simpler and more natural (to its author, at least ;-). That said, see the considerations below.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Sorry, I forgot to mention it here, but the page does mention it at the top:</p>
<blockquote><p>
There&#8217;s also a plugin (link) available offering similar functionality. cobzr differs from the plugin by using a command set similar to git and by hiding away the visible difference between a branch with co-location and one without. Commands always work, and the tree is adapted to co-location the first time multiple branches are requested, so usage is simpler and more natural (to its author, at least <img src='http://blog.labix.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> . That said, see the considerations below.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Jelmer Vernooij</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119061</link>
		<dc:creator>Jelmer Vernooij</dc:creator>
		<pubDate>Mon, 16 Jan 2012 11:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119061</guid>
		<description>From looking at the code, it seems it does indeed do pretty much the same thing as bzr-colo, except it stores branches in .bzr/cobzr rather than .bzr/branches as bzr-colo does.</description>
		<content:encoded><![CDATA[<p>From looking at the code, it seems it does indeed do pretty much the same thing as bzr-colo, except it stores branches in .bzr/cobzr rather than .bzr/branches as bzr-colo does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by ?ukasz</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119053</link>
		<dc:creator>?ukasz</dc:creator>
		<pubDate>Mon, 16 Jan 2012 09:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119053</guid>
		<description>I&#039;ve been using bzr-colo plugin for almost a year now. So far no issues with it.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using bzr-colo plugin for almost a year now. So far no issues with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bazaar, the git way by Martin Pool</title>
		<link>http://blog.labix.org/2012/01/16/bazaar-the-git-way/comment-page-1#comment-119047</link>
		<dc:creator>Martin Pool</dc:creator>
		<pubDate>Mon, 16 Jan 2012 06:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=935#comment-119047</guid>
		<description>This looks pretty similar to bzr-colo - how does that differ? http://doc.bazaar.canonical.com/plugins/en/colo-plugin.html</description>
		<content:encoded><![CDATA[<p>This looks pretty similar to bzr-colo &#8211; how does that differ? <a href="http://doc.bazaar.canonical.com/plugins/en/colo-plugin.html" rel="nofollow">http://doc.bazaar.canonical.com/plugins/en/colo-plugin.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Good concurrency changes the game by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2011/12/12/good-concurrency-changes-the-game/comment-page-1#comment-114624</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Mon, 12 Dec 2011 22:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=886#comment-114624</guid>
		<description>Antti,

It&#039;s comparatively simpl&lt;i&gt;er&lt;/i&gt; indeed, and more usual for people not familiar with Go syntax and semantics. The point made is that the concurrent version is trivial as well, assuming familiarity with the syntax and semantics of the language.</description>
		<content:encoded><![CDATA[<p>Antti,</p>
<p>It&#8217;s comparatively simpl<i>er</i> indeed, and more usual for people not familiar with Go syntax and semantics. The point made is that the concurrent version is trivial as well, assuming familiarity with the syntax and semantics of the language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Good concurrency changes the game by Antti Rasinen</title>
		<link>http://blog.labix.org/2011/12/12/good-concurrency-changes-the-game/comment-page-1#comment-114622</link>
		<dc:creator>Antti Rasinen</dc:creator>
		<pubDate>Mon, 12 Dec 2011 21:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=886#comment-114622</guid>
		<description>Thank you! This was most enlightening.

I must admit that I found the serial version easier to read and understand. I still live in the single-core mindset, I suppose.

 The goroutined version naturally does look very simple for a concurrent solution.</description>
		<content:encoded><![CDATA[<p>Thank you! This was most enlightening.</p>
<p>I must admit that I found the serial version easier to read and understand. I still live in the single-core mindset, I suppose.</p>
<p> The goroutined version naturally does look very simple for a concurrent solution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

