<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>InqBlot &#187; git</title>
	<atom:link href="http://blogs.inquirium.net/blot/tag/git/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.inquirium.net/blot</link>
	<description>Inquirium on Learning, Technology, and Design</description>
	<lastBuildDate>Tue, 13 Sep 2011 17:59:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Branching model for distributed version control</title>
		<link>http://blogs.inquirium.net/blot/2010/01/branching-model-for-distributed-version-control/</link>
		<comments>http://blogs.inquirium.net/blot/2010/01/branching-model-for-distributed-version-control/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 19:22:30 +0000</pubDate>
		<dc:creator>eric</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[hg]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false">http://blogs.inquirium.net/blot/?p=89</guid>
		<description><![CDATA[We&#8217;re in the process of transitioning from Subversion to Mercurial, and one of the challenges is defining a coordinated framework for managing development work. Subversion essentially came with an &#8216;official&#8217; branches/tags/trunk model, as well as a central repository location, but the distributed landscape seems more wide open. (Granted, that&#8217;s part of the appeal.) The Git [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re in the process of transitioning from <a href="http://subversion.tigris.org/">Subversion</a> to <a href="http://mercurial.selenic.com/">Mercurial</a>, and one of the challenges is defining a coordinated framework for managing development work. Subversion essentially came with an &#8216;official&#8217; branches/tags/trunk model, as well as a central repository location, but the distributed landscape seems more wide open. (Granted, that&#8217;s part of the appeal.) The <a href="http://nvie.com/archives/323">Git model described here</a> is a nice step forward, and seems to apply to Mercurial as well as Git.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.inquirium.net/blot/2010/01/branching-model-for-distributed-version-control/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

