<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Mercurial vs. Subversion, take 2</title>
	<atom:link href="http://seeknuance.com/2010/03/06/mercurial-vs-subversion-take-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://seeknuance.com/2010/03/06/mercurial-vs-subversion-take-2/</link>
	<description>Python, Django, technology, Seattle, careers, life, et cetera...</description>
	<lastBuildDate>Sun, 05 Feb 2012 01:48:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: John</title>
		<link>http://seeknuance.com/2010/03/06/mercurial-vs-subversion-take-2/#comment-1851</link>
		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Tue, 09 Mar 2010 00:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://seeknuance.com/?p=4867#comment-1851</guid>
		<description><![CDATA[The Creole syntax was based on a careful analysis of existing wikis&#039;, and lots of thought appears to have gone into it. Nonetheless, or maybe because of this, it feels like a camel, i.e., a horse designed by a committee. The way links and lists are handled feels odd. And it could be smarter about where it puts inter-line whitespace in the output.

Having said that, I&#039;m fine with development wikis being &quot;minimalistic&quot; and favoring content over form. I can definitely live with Creole, but I think for example that Trac&#039;s wiki syntax was a little more logical.

I would love to see you write article(s) about using the latest generations of online collaboration tools!]]></description>
		<content:encoded><![CDATA[<p>The Creole syntax was based on a careful analysis of existing wikis&#8217;, and lots of thought appears to have gone into it. Nonetheless, or maybe because of this, it feels like a camel, i.e., a horse designed by a committee. The way links and lists are handled feels odd. And it could be smarter about where it puts inter-line whitespace in the output.</p>
<p>Having said that, I&#8217;m fine with development wikis being &#8220;minimalistic&#8221; and favoring content over form. I can definitely live with Creole, but I think for example that Trac&#8217;s wiki syntax was a little more logical.</p>
<p>I would love to see you write article(s) about using the latest generations of online collaboration tools!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://seeknuance.com/2010/03/06/mercurial-vs-subversion-take-2/#comment-1850</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Sun, 07 Mar 2010 20:17:45 +0000</pubDate>
		<guid isPermaLink="false">http://seeknuance.com/?p=4867#comment-1850</guid>
		<description><![CDATA[A couple of tidbits - 

1) did you know that you can use Mercurial to work with GitHub too? Not a very common scenario, but if you wanted to do that the GitHub folks have written a hg-git plugin thingy to allow you to check out and push back to Git repositories. Then again, it can just add a shitload of confusion to the mix.

2) what don&#039;t you like about BitBucket&#039;s wiki? What would you change? I&#039;m curious for myself more than anything else - I&#039;ve found that GitHub&#039;s ability to recognize Markdown, Restructured Text, Textile, and other mechanisms and displays them in a rich format to be really freakin&#039; useful, and has negated a lot of the Wiki need for me (see http://github.com/ccgus/letters/blob/master/README-CONTRIB.markdown for an example)

I want to, and haven&#039;t yet, written an article exactly like this on how to collaborate (common things you&#039;ll want/need to do with step-by-step how to) for BitBucket. 

I really like BitBucket, if nothing else than it&#039;s focused on Mercurial (which I also like) and I want to see Jesper&#039;s work continue to grow.]]></description>
		<content:encoded><![CDATA[<p>A couple of tidbits &#8211; </p>
<p>1) did you know that you can use Mercurial to work with GitHub too? Not a very common scenario, but if you wanted to do that the GitHub folks have written a hg-git plugin thingy to allow you to check out and push back to Git repositories. Then again, it can just add a shitload of confusion to the mix.</p>
<p>2) what don&#8217;t you like about BitBucket&#8217;s wiki? What would you change? I&#8217;m curious for myself more than anything else &#8211; I&#8217;ve found that GitHub&#8217;s ability to recognize Markdown, Restructured Text, Textile, and other mechanisms and displays them in a rich format to be really freakin&#8217; useful, and has negated a lot of the Wiki need for me (see <a href="http://github.com/ccgus/letters/blob/master/README-CONTRIB.markdown" rel="nofollow">http://github.com/ccgus/letters/blob/master/README-CONTRIB.markdown</a> for an example)</p>
<p>I want to, and haven&#8217;t yet, written an article exactly like this on how to collaborate (common things you&#8217;ll want/need to do with step-by-step how to) for BitBucket. </p>
<p>I really like BitBucket, if nothing else than it&#8217;s focused on Mercurial (which I also like) and I want to see Jesper&#8217;s work continue to grow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rock Hymas</title>
		<link>http://seeknuance.com/2010/03/06/mercurial-vs-subversion-take-2/#comment-1849</link>
		<dc:creator><![CDATA[Rock Hymas]]></dc:creator>
		<pubDate>Sun, 07 Mar 2010 04:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://seeknuance.com/?p=4867#comment-1849</guid>
		<description><![CDATA[Bravo, John. I hope I am as magnanimous when making a self-correction. Also, with your follow up I would say you&#039;ve found nuance. And as a former Microsoftie, I wouldn&#039;t be sad to see your prediction about Ballmer come true.]]></description>
		<content:encoded><![CDATA[<p>Bravo, John. I hope I am as magnanimous when making a self-correction. Also, with your follow up I would say you&#8217;ve found nuance. And as a former Microsoftie, I wouldn&#8217;t be sad to see your prediction about Ballmer come true.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

