<?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 on: Using Mercurial To Manage Subversion</title>
	<atom:link href="http://agoln.net/archives/95/feed" rel="self" type="application/rss+xml" />
	<link>http://agoln.net/archives/95</link>
	<description>Development and personal site</description>
	<lastBuildDate>Wed, 12 May 2010 16:55:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Frank</title>
		<link>http://agoln.net/archives/95/comment-page-1#comment-4493</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Tue, 18 Aug 2009 16:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://agoln.net/archives/95#comment-4493</guid>
		<description>Good article, thank you. 

I also wanted to note that Luke&#039;s last link is dead... The one enclosing the text &quot;Mercurial has a few perceived downsides&quot;</description>
		<content:encoded><![CDATA[<p>Good article, thank you. </p>
<p>I also wanted to note that Luke&#8217;s last link is dead&#8230; The one enclosing the text &#8220;Mercurial has a few perceived downsides&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logan</title>
		<link>http://agoln.net/archives/95/comment-page-1#comment-1526</link>
		<dc:creator>Logan</dc:creator>
		<pubDate>Thu, 13 Mar 2008 00:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://agoln.net/archives/95#comment-1526</guid>
		<description>Luke,

Thanks for pointing that out.  For some reason your comment was held for approval because it thought it was spam, so I didn&#039;t see it right away.  Have you passed a turing test lately? Maybe once disqus allows importing of comments, I&#039;ll use it :P</description>
		<content:encoded><![CDATA[<p>Luke,</p>
<p>Thanks for pointing that out.  For some reason your comment was held for approval because it thought it was spam, so I didn&#8217;t see it right away.  Have you passed a turing test lately? Maybe once disqus allows importing of comments, I&#8217;ll use it <img src='http://agoln.net/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://agoln.net/archives/95/comment-page-1#comment-1450</link>
		<dc:creator>Luke Hoersten</dc:creator>
		<pubDate>Fri, 07 Mar 2008 05:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://agoln.net/archives/95#comment-1450</guid>
		<description>Distributed revision control can be thought of as a repository of repositories so its not a far leap to wrap a svn repo in hg.

Anyway, when you say that &quot;in Mercurial if you wish to make a branch, you simply hg clone it.&quot; This isn&#039;t entirely correct. Cloning makes a &lt;em&gt;whole new tree&lt;/em&gt; (repo), branches and all. So you &lt;em&gt;do&lt;/em&gt; effectively get a new branch, but also a whole new tree. The easier and more appropriate way to branch is with the branch command. It creates a new branch in the current repository. Using clone to branch is intended for something called &quot;&lt;a href=&quot;http://hgbook.red-bean.com/hgbookch8.html#x12-1620008.2&quot; rel=&quot;nofollow&quot;&gt;big-picture branch&lt;/a&gt;&quot; (like a major 1.0 release) which is not in the spirit of cheap branching. &quot;Small-picture branches&quot; can be used for every little feature etc. Small-picture branches are the bread and butter of Hg. 

Finally, &lt;a href=&quot;http://openradix.org/archives/349&quot; rel=&quot;nofollow&quot;&gt;Mercurial has a few perceived downsides&lt;/a&gt;. They aren&#039;t fundamental show-stoppers but they are hurtles that some aren&#039;t willing to take on in order to get a better revision control model.</description>
		<content:encoded><![CDATA[<p>Distributed revision control can be thought of as a repository of repositories so its not a far leap to wrap a svn repo in hg.</p>
<p>Anyway, when you say that &#8220;in Mercurial if you wish to make a branch, you simply hg clone it.&#8221; This isn&#8217;t entirely correct. Cloning makes a <em>whole new tree</em> (repo), branches and all. So you <em>do</em> effectively get a new branch, but also a whole new tree. The easier and more appropriate way to branch is with the branch command. It creates a new branch in the current repository. Using clone to branch is intended for something called &#8220;<a href="http://hgbook.red-bean.com/hgbookch8.html#x12-1620008.2" rel="nofollow">big-picture branch</a>&#8221; (like a major 1.0 release) which is not in the spirit of cheap branching. &#8220;Small-picture branches&#8221; can be used for every little feature etc. Small-picture branches are the bread and butter of Hg. </p>
<p>Finally, <a href="http://openradix.org/archives/349" rel="nofollow">Mercurial has a few perceived downsides</a>. They aren&#8217;t fundamental show-stoppers but they are hurtles that some aren&#8217;t willing to take on in order to get a better revision control model.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

